jest: Cannot npm install jest Error: 404 Not Found: @babel/code-frame@^7.0.0-beta.35

Do you want to request a feature or report a bug? Bug

What is the current behavior?

npm i -DE --no-cache  jest
npm ERR! code E404
npm ERR! 404 Not Found: @babel/code-frame@^7.0.0-beta.35

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test. The latest available beta on github seems to be 34. So you guys are asking for a non-existant package https://github.com/babel/babel/blob/830c527bb7873b29f671a3568b21b4a6af98ceda/packages/babel-code-frame/README.md

What is the expected behavior? No error

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system. node v8.9.1 npm v5.5.1

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 6
Comments: 23 (5 by maintainers)

Most upvoted comments

Still happening.

+12

alexanderkjeldaas on Jan 24, 2018

We reference an internal NPM repository, so I wondered if that was not resolving the dependency correctly. Adding this to my .npmrc seemed to resolve the situation.

@babel:registry=https://registry.npmjs.org

+11

ryaanwells on Jan 29, 2018

npm install xxxx --registry=http://registry.npmjs.org solved my issue.

iver3on on Dec 6, 2018

I fought this problem for about an hour this morning; I had an _auth string in my npm config that wasn’t letting me install anything. Even if you add @babel:registry=https://my.registry.com it doesn’t work with the (I’m guessing) unnecessary _auth param.

EDIT: I also tried downgrading to 7.x.x and the installation didn’t work, to clarify.

byamj on Apr 10, 2018

I had the same issue. I confirm that removing _auth param in .npmrc fixes that issue.

mianor64 on Apr 24, 2018

it definitely is, please check your npmrc for custom registry

SimenB on Mar 27, 2018

No plans for a patch.

Does everybody with issues use private registries or a proxy in front of the registry? At work we had issues with our proxy, as it unescaped %2f meaning it put a literal / in the url turning it into a path (thus giving us 404). I don’t remember the particulars (I can dig into our infrastructure code later if anybody thinks it’d help), but we basically turned off path decoding.

For private registries, I’d try adding @babel:registry=https://my.registry.com to .npmrc. It’s not a scalable solution (if it even makes any difference) but might help.

SimenB on Feb 27, 2018

Seems like they’ve changed their permission model, however this URL works: https://registry.npmjs.org/@babel%2Fcode-frame

SimenB on Feb 21, 2018