✖ Cannot read property 'length' of undefined
See original GitHub issuenp errors on np
np
Warning: No files field specified in package.json nor is a .npmignore file present. Having one of those will prevent you present. Having one of those will prevent you from accidentally publishinackage's source code to npm.g development-specific files along with your package's source code to npm.
✖ Cannot read property 'length' of undefined
Environment
np - can’t get version, but fresh install Node.js - 15.14.0 npm - 7.5.0 Git - 2.24.0.windows.2 OS - Windows 10
Volta - 1.0.2
Issue Analytics
- State:
- Created 2 years ago
- Reactions:15
- Comments:8
Top Results From Across the Web
TypeError: Cannot read property 'length' of Undefined in JS
The "Cannot read property 'length' of undefined" error occurs when accessing the length property on an undefined value. To solve the error, ...
Read more >Cannot read properties of undefined (reading 'length') - TrackJS
This message indicates that our code expects to have an object with a length property, but that object was not present. length is...
Read more >Typeerror: Cannot Read Property 'length' of Undefined
A typeerror length of undefined can indicate that the actual type of an operand is different from the expected type. This error can...
Read more >[SOLVED] Cannot Read Property 'length' of Undefined in JS
4 Quick Fixes for the “Cannot Read Property 'length' of Undefined” Error in JavaScript · 1. Use an if Statement · 2. Use...
Read more >Cannot read property length of undefined - Stack Overflow
The error means that what ever element is returned by getElementById('WallSearch') , it does not have a value property. Every form field has...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have the same issue. It is on an new repo. (I’m first time np user…) node.js - v14.17.5 / v16.8.0 npm - 7.21.1 git - 2.32.0.windows.2 / 2.33.0.windows.2 np installed today (
np -v
instantly produces the error) windows 10 running commands from vscode powershell terminal.Update
After first running
npm publish
to create the inital package, np can be used.@dopecodez I honestly can’t remember. If I come across the bug error again, I’ll let you know.