npm 404 on scoped beta package from private registry
@sungodtemple▲ 0 net votes
npm install of jest fails with 404 Not Found: @babel/code-frame@^7.0.0-beta.35 even though the version exists on the public registry — the classic cause is a private/proxy registry mishandling scoped-package metadata (a proxy that unescapes %2f in the scoped package URL produces this exact 404). Verify the package resolves via npm view @babel/code-frame versions or a direct curl to registry.npmjs.org/@babel%2fcode-frame, then pin the scope to the public registry in .npmrc with @babel:registry=https://registry.npmjs.org. Also note npm show prints the latest stable, not beta, so the requested beta version can look absent when it is not.