[BUG] Cannot read properties of undefined (reading 'spec') #4819

Activity

1. talatkuyuk

   added

   Bugthing that needs fixingthing that needs fixing

   Needs Triageneeds review for next stepsneeds review for next steps

   Release 8.xwork is associated with a specific npm 8 releasework is associated with a specific npm 8 release

   on Apr 28, 2022
2. PedroC88 commented on Apr 28, 2022

   

   PedroC88

   on Apr 28, 2022

   More actions

   I'm having the same error installing ADF Utilities:

   package.json

   {
       "scripts": {
           "build": "node node_modules/@microsoft/azure-data-factory-utilities/lib/index"
       },
       "dependencies": {
           "@microsoft/azure-data-factory-utilities": "^0.1.5"
       }
   }
   

   npm version

   {
     npm: '8.8.0',
     node: '16.15.0',
     [...]
   }
   

   logs

   0 verbose cli C:\Program Files\nodejs\node.exe C:\Users\username\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
   1 info using npm@8.8.0
   2 info using node@v16.15.0
   3 timing npm:load:whichnode Completed in 0ms
   4 timing config:load:defaults Completed in 2ms
   5 timing config:load:file:C:\Users\username\AppData\Roaming\npm\node_modules\npm\npmrc Completed in 3ms
   6 timing config:load:builtin Completed in 3ms
   7 timing config:load:cli Completed in 1ms
   8 timing config:load:env Completed in 1ms
   9 timing config:load:file:C:\Users\username\source\repos\project\.npmrc Completed in 0ms
   10 timing config:load:project Completed in 2ms
   11 timing config:load:file:C:\Users\username\.npmrc Completed in 0ms
   12 timing config:load:user Completed in 1ms
   13 timing config:load:file:C:\Users\username\AppData\Roaming\npm\etc\npmrc Completed in 0ms
   14 timing config:load:global Completed in 0ms
   15 timing config:load:validate Completed in 0ms
   16 timing config:load:credentials Completed in 1ms
   17 timing config:load:setEnvs Completed in 1ms
   18 timing config:load Completed in 12ms
   19 timing npm:load:configload Completed in 12ms
   20 timing npm:load:mkdirpcache Completed in 1ms
   21 timing npm:load:mkdirplogs Completed in 0ms
   22 verbose title npm install .\pipelines\
   23 verbose argv "install" ".\\pipelines\\"
   24 timing npm:load:setTitle Completed in 2ms
   25 timing config:load:flatten Completed in 3ms
   26 timing npm:load:display Completed in 5ms
   27 verbose logfile logs-max:10 dir:C:\Users\username\AppData\Local\npm-cache\_logs
   28 verbose logfile C:\Users\username\AppData\Local\npm-cache\_logs\2022-04-28T14_42_58_414Z-debug-0.log
   29 timing npm:load:logFile Completed in 6ms
   30 timing npm:load:timers Completed in 0ms
   31 timing npm:load:configScope Completed in 0ms
   32 timing npm:load Completed in 27ms
   33 timing arborist:ctor Completed in 1ms
   34 silly logfile start cleaning logs, removing 2 files
   35 timing arborist:ctor Completed in 0ms
   36 silly logfile done cleaning log files
   37 timing idealTree:init Completed in 13ms
   38 timing idealTree:userRequests Completed in 5ms
   39 silly idealTree buildDeps
   40 silly placeDep ROOT undefined@ OK for:  want: file:pipelines
   41 timing idealTree:#root Completed in 7ms
   42 timing idealTree:node_modules/undefined Completed in 0ms
   43 silly fetch manifest @microsoft/azure-data-factory-utilities@^0.1.5
   44 http fetch GET 200 https://registry.npmjs.org/@microsoft%2fazure-data-factory-utilities 18ms (cache hit)
   45 silly placeDep ROOT @microsoft/azure-data-factory-utilities@0.1.6 OK for: pipelines want: ^0.1.5
   46 silly fetch manifest commander@6.2.0
   47 http fetch GET 200 https://registry.npmjs.org/commander 9ms (cache hit)
   48 timing idealTree:pipelines Completed in 38ms
   49 silly placeDep ROOT commander@6.2.0 OK for: @microsoft/azure-data-factory-utilities@0.1.6 want: 6.2.0
   50 timing idealTree:node_modules/@microsoft/azure-data-factory-utilities Completed in 3ms
   51 timing idealTree:node_modules/commander Completed in 0ms
   52 timing idealTree:buildDeps Completed in 49ms
   53 timing idealTree:fixDepFlags Completed in 1ms
   54 timing idealTree Completed in 69ms
   55 timing reify:loadTrees Completed in 70ms
   56 timing reify:diffTrees Completed in 1ms
   57 silly reify moves {}
   58 timing reify:retireShallow Completed in 1ms
   59 timing reify:createSparse Completed in 3ms
   60 timing reify:loadBundles Completed in 0ms
   61 silly audit bulk request {
   61 silly audit   '@microsoft/azure-data-factory-utilities': [ '0.1.6' ],
   61 silly audit   commander: [ '6.2.0' ]
   61 silly audit }
   62 timing reifyNode:node_modules/undefined Completed in 28ms
   63 timing reifyNode:node_modules/@microsoft/azure-data-factory-utilities Completed in 56ms
   64 timing reifyNode:node_modules/commander Completed in 58ms
   65 timing reify:unpack Completed in 58ms
   66 timing reify:unretire Completed in 0ms
   67 timing build:queue Completed in 1ms
   68 timing build:deps Completed in 1ms
   69 timing build:queue Completed in 0ms
   70 timing build:links Completed in 0ms
   71 timing build Completed in 1ms
   72 timing reify:build Completed in 1ms
   73 timing reify:trash Completed in 0ms
   74 timing command:install Completed in 153ms
   75 verbose stack TypeError: Cannot read properties of undefined (reading 'spec')
   75 verbose stack     at updateNodes (C:\Users\username\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:1177:44)
   75 verbose stack     at Arborist.[saveIdealTree] (C:\Users\username\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:1344:11)
   75 verbose stack     at Arborist.reify (C:\Users\username\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:156:31)
   75 verbose stack     at async Install.exec (C:\Users\username\AppData\Roaming\npm\node_modules\npm\lib\commands\install.js:156:5)
   75 verbose stack     at async module.exports (C:\Users\username\AppData\Roaming\npm\node_modules\npm\lib\cli.js:78:5)
   76 verbose cwd C:\Users\username\source\repos\project
   77 verbose Windows_NT 10.0.22000
   78 verbose node v16.15.0
   79 verbose npm  v8.8.0
   80 error Cannot read properties of undefined (reading 'spec')
   81 verbose exit 1
   82 timing npm Completed in 295ms
   83 verbose unfinished npm timer reify 1651156978554
   84 verbose unfinished npm timer reify:audit 1651156978639
   85 verbose unfinished npm timer auditReport:getReport 1651156978640
   86 verbose unfinished npm timer reify:save 1651156978704
   87 verbose code 1
   88 error A complete log of this run can be found in:
   88 error     C:\Users\username\AppData\Local\npm-cache\_logs\2022-04-28T14_42_58_414Z-debug-0.log
   
3. PedroC88 commented on Apr 28, 2022

   

   PedroC88

   on Apr 28, 2022

   Last edited by PedroC88

   More actions

   Alright, so here's a bit more detail, perhaps it's a layer-8 error?

   • With the package.json at the root label the npm install command runs successfully
   • With the package.json file in the pipelines folder and running npm install from the pipelines folder it runs successfully
   • With the package.json file in the pipelines folder and running npm install .\pipelines from the root folder it fails

   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

   👍React with 👍1Reacted by Wallace Kelly
4. Jeremy-coding commented on Aug 27, 2022

   

   Jeremy-coding

   on Aug 27, 2022

   Last edited by Jeremy-coding

   More actions

   I'm also getting this error. I'm on npm 8.11.0.

   $ npm install https://github.com/JeremyEllingham/webassemblyjs --loglevel verbose
   
   ...
   npm timing reify:trash Completed in 165ms
   npm timing command:install Completed in 129049ms
   npm verb stack TypeError: Cannot read properties of undefined (reading 'spec')
   npm verb stack     at updateNodes (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:1178:44)
   npm verb stack     at Arborist.[saveIdealTree] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:1345:11)
   npm verb stack     at Arborist.reify (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:156:31)
   npm verb stack     at async Install.exec (/usr/local/lib/node_modules/npm/lib/commands/install.js:156:5)
   npm verb stack     at async module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:78:5)
   npm verb cwd /Users/jeremy/project/selene-wallet
   npm verb Darwin 21.6.0
   npm verb node v16.16.0
   npm verb npm  v8.11.0
   npm ERR! Cannot read properties of undefined (reading 'spec')
   npm verb exit 1
   npm timing npm Completed in 129220ms
   npm verb unfinished npm timer reify 1661607103046
   npm verb unfinished npm timer reify:save 1661607232091
   npm verb code 1
   
   npm ERR! A complete log of this run can be found in:
   npm ERR!     /Users/jeremy/.npm/_logs/2022-08-27T13_31_42_874Z-debug-0.log
   

   Should be reproducible for anyone else.
5. WilcoFiers commented on Sep 5, 2022

   

   WilcoFiers

   on Sep 5, 2022

   More actions

   Had this issue too. The problem turned out to come from package.json not having a name property. Adding that in solved the issue for me.

   👍React with 👍30Reacted by Karan Singhasane, Tim Marois, Yun Shan, Charles-Henri Arnould, Ryan Grieb, Kai Ase Siren, Wallace Kelly, Alessandro Gentili, Kevin Bergin, Sasha :) and 20 more

   👎React with 👎1Reacted by Carlos Zúñiga

   ❤️React with ❤️10Reacted by Jørgen Solli, Tim Marois, Sarthik Gupta, Kai Ase Siren, Fahd Arafat, Guri, Sebastian Schwarz, Jakub Wróbel, Om Singh Mehta and Trey
6. corngood commented on Sep 5, 2022

   

   corngood

   on Sep 5, 2022

   More actions

   For me, this was caused by having node.exe next to package.json in the root of our tree. Moving it into any other directory fixed the problem. NPM treats wherever the node binary lives as the 'distro root' and does some special magic.
7. daniel-rebolledo commented on Oct 13, 2022

   

   daniel-rebolledo

   on Oct 13, 2022

   More actions

   I have the same problem, in my case running npm install react react-dom. On my package.json I have these two packages as peerDependencies, if I move those to devDependencies and then run npm install the error is gone and all the packages are installed. I always have to move back those packages to peerDependencies after that.

   npm: 8.11.0
   node: 16.15.1

   👍React with 👍15Reacted by Scooby, armoni-itay, Daniele Mazzotta, Kari Söderholm, Pooya Oladazimi, Pavel Gurecki, David Welling, Michael McNees, Hamou Ait Abderrahim, Max Waibel and 5 more

   ❤️React with ❤️20Reacted by Prathyush_s, Filip, ElfenLiedGH, Charlie Blevins, Tim Osborn, Chris Howard, njetsy, Jiasheng Wu, Skol, Scooby and 10 more
8. prathyushSunny commented on Oct 14, 2022

   

   prathyushSunny

   on Oct 14, 2022

   More actions

   @daniel-rebolledo Thanks! Your approached resolved it. I had the same issue while doing npm i react but not anymore.
9. que273 commented on Oct 21, 2022

   

   que273

   on Oct 21, 2022

   More actions

   I appear to have the same issue as @daniel-rebolledo with peerDependencies. Oddly for me it was working with registry.npmjs.org but not when I switched to a private mirror registry. The issue went away when I specified the //legacy-peer-deps=true option to the registry in .npmrc

   👍React with 👍2Reacted by Bert Verhelst and Skol
10. Shhad commented on Nov 11, 2022

    

    Shhad

    on Nov 11, 2022

    More actions

    @que273 yes! I have same config field in .npmrc . Do you know why it behaves like that?
11. zloirock commented on Nov 12, 2022

    

    zloirock

    on Nov 12, 2022

    Last edited by zloirock

    More actions

    I have this issue after moving cd path && npm i -> npm i --prefix path, https://github.com/zloirock/core-js/actions/runs/3452139442/jobs/5761893828, diff: zloirock/core-js@e503cc2

    😄React with 😄1Reacted by Michael Kochell
12. JonathanMerklin commented on Mar 22, 2023

    

    JonathanMerklin

    on Mar 22, 2023

    More actions

    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 chai-enzyme regardless of whether it was a peer or dev dependency.

    Fortunately, for us, we weren't really "using" chai-enzyme in the module or in anything we owned, so we were able to just throw in the migration guide "no longer including chai-enzyme, and since you should prefer <alternativeMoreModernLibrariesAndMechanismsForUnitTestingWeAreUsingInOtherPlaces />, if you are using chai-enzyme in your extant test code, you're on your own".

    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.
13. ph3rro commented on Mar 27, 2023

    

    ph3rro

    on Mar 27, 2023

    More actions

    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
    Forked version: https://github.com/sickopickle/react-native-draw

    I made no changes so I don't know why this would happen.
14. ami-momo commented on Sep 8, 2024

    

    ami-momo

    on Sep 8, 2024

    Last edited by ami-momo

    More actions

    This happened to me when I wanted to use npx somecommand from my package, but my package did not have the name property in package.json and caused this error:

    npm error Cannot read properties of undefined (reading 'spec')
    

    Though bunx did not have any problem, but it seems it caused error using npx
15. mwaibel-go commented on Nov 26, 2024

    

    mwaibel-go

    on Nov 26, 2024

    More actions

    I’m currently facing this issue with npm version 10.9.1. I have no idea what might be causing this in my case.
16. wu-lee commented on Jan 7, 2026

    

    wu-lee

    on Jan 7, 2026

    Last edited by wu-lee

    More actions

    I'm seeing this error too.

    Situation: installing a package directly from GitHub.

    npm install <account name>/<repo name>#<commit-id>
    

    Versions:

    npm --version
    11.5.1
    node --version
    v24.7.0
    

    Same error, but the message "A complete log of this run can be found in" references a non-existing file.

    The installed package is one with workspaces, which have "name" and "version" attributes, and but the top-level package.json does not have the "name" attribute. (It is not marked private.)

    Adding "name" to the top-level package.json leads to a failure with:

    npm error Invalid Version:
    

    (No value given after "Version")

    But adding a "version" attribute does get to a successful install!

    So it does appear to be that the code is making unguarded assumptions about the package.json fields present.

    There are still some warnings, which may be unrelated:

    npm warn ERESOLVE overriding peer dependency
    npm warn While resolving: @swc-node/core@1.14.1
    npm warn Found: @swc/core@1.5.29
    npm warn node_modules/@swc/core
    npm warn   dev @swc/core@"~1.5.7" from the root project
    npm warn   2 more (@swc-node/register, nx)
    npm warn
    npm warn Could not resolve dependency:
    npm warn peer @swc/core@">= 1.13.3" from @swc-node/core@1.14.1
    npm warn node_modules/@swc-node/register/node_modules/@swc-node/core
    npm warn   @swc-node/core@"^1.13.1" from @swc-node/register@1.9.2
    npm warn   node_modules/@swc-node/register
    npm warn
    npm warn Conflicting peer dependency: @swc/core@1.15.8
    npm warn node_modules/@swc/core
    npm warn   peer @swc/core@">= 1.13.3" from @swc-node/core@1.14.1
    npm warn   node_modules/@swc-node/register/node_modules/@swc-node/core
    npm warn     @swc-node/core@"^1.13.1" from @swc-node/register@1.9.2
    npm warn     node_modules/@swc-node/register
    
17. wu-lee

    added 2 commits that reference this issue on Jan 7, 2026

    package.json - add name, version and module fields

    ...

    0fcb725

    package.json - add name, version and module fields

    ...

    5f0730b
18. wu-lee

    added a commit that references this issue on Mar 14, 2026

    package.json - add name, version and module fields

    ...

    f9d891e
19. wu-lee

    added a commit that references this issue on Mar 27, 2026

    package.json - add name, version and module fields

    ...

    632c8f7
20. nkolev92

    added

    Priority 2secondary priority issuesecondary priority issue

    Priority 3

    and removed

    Priority 2secondary priority issuesecondary priority issue

    on Oct 21, 2026
21. mvanhorn commented on Oct 22, 2026

    

    mvanhorn

    on Oct 22, 2026

    Contributor

    More actions

    An add spec that arrives without a name is meant to take that name from the fetched manifest. When the manifest name is missing or an empty string, the dependency is stored under the key "undefined" and no outgoing edge is created.

    After the manifest is loaded, a spec that still has no name and whose manifest name is missing or empty throws EMISSINAME, carrying the raw spec, before that dependency is recorded. Explicit-request collection adds an edge only when edgesOut returns one.

    #10154