-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Cannot read properties of undefined (reading 'spec') #4819
Comments
I'm having the same error installing ADF Utilities:
|
Alright, so here's a bit more detail, perhaps it's a layer-8 error?
I also realized that even with the error the packages are (or appear to be) restored. P.S. this is all running on a Windows 11 Terminal with a PowerShell 7.2.3 session |
I had this issue too. The problem was because when I started a proyect (Alpinejsx) I inmediatly used The solution was to use first |
I'm also getting this error. I'm on npm 8.11.0.
Should be reproducible for anyone else. |
Had this issue too. The problem turned out to come from package.json not having a |
For me, this was caused by having |
I have the same problem, in my case running npm: 8.11.0 |
@daniel-rebolledo Thanks! Your approached resolved it. I had the same issue while doing |
I appear to have the same issue as @daniel-rebolledo with peerDependencies. Oddly for me it was working with |
@que273 yes! I have same config field in |
I have this issue after moving |
Thought I'd call out that I was experiencing this when migrating a module (in our internal registry) to be built in and compatible with Node 18 / the latest NPM (the module had been around since the Node 0.x days, and its purpose was "install this one package as a devDependency in order to get a bunch of unit testing tooling packages at once") and was receiving this when trying to install Fortunately, for us, we weren't really "using" The point: if you're running into this, you could try removing individual packages one-at-a-time (and then in pairs, and then in triplets, etc.) until you no longer see this behavior, to isolate a problem dependency or set thereof, but from there the prescription would be entirely context-dependent. |
I have this issue when I fork a package. The original package installs fine, but the forked version doesn't. Original version: https://github.com/BenJeau/react-native-draw I made no changes so I don't know why this would happen. |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I develop a nextjs application. I want to use react-table package specific version from github. I tried the below command in the terminal:
It starts to download but stucked after a while and ended with the error
Cannot read properties of undefined (reading 'spec')
Here is the npm log:
Expected Behavior
I expect the npm install the react-table package from GitHub
Steps To Reproduce
Cannot read properties of undefined (reading 'spec')
Environment
The text was updated successfully, but these errors were encountered: