Developer finds npm warnings, CI glob quirks, and registry surprises shipping tiny package

A developer publishing a 200-line npm package called video-bitrate-calculator encountered three misleading tooling issues during the release process. An npm warning claimed CLI entry points were deleted during publish, but reading npm's own source code revealed the paths were merely normalized and the entries remained intact. In CI testing, quoted glob patterns in the test script worked on Node 22 but silently matched nothing on Node 18 and 20, meaning newer Node versions masked a real coverage gap rather than catching it. The fix was to drop the glob entirely and let the Node test runner discover test files automatically, ensuring consistent behavior across versions. A third surprise involved npm login unexpectedly opening a signup page for an unfamiliar registry, highlighting how default tooling assumptions can mislead developers into unnecessary or incorrect actions.