Missing version in package.json
See original GitHub issueThe package.json
file is very bare bones here and doesn’t even have a version number.
version is a required field
Yarn refuses to install packages that do not have a version number specified and just throws a error Can't add "esptool-js": invalid package version undefined.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
npm can't find package.json - Stack Overflow
I think, npm init will create your missing package.json file. It works for me for the same case.
Read more >missing version in package.json throws error with yarn #113
When trying to install the dependencies of the headless front end (assets/headless) with yarn, there is an error thrown, ...
Read more >package.json - npm Docs
json are the name and version fields as they will be required. The name and version together form an identifier that is assumed...
Read more >Recover missing package.json with npm-collect
I recently took over a spare time project with multiple Git repos and branches where the package.json had been removed from all branches ......
Read more >package.json - Yarn
The two most important fields in your package.json are name and version , without them your package won't be able to install. The...
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 FreeTop 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
Top GitHub Comments
done
Edit: On a side note, publishing this package to npmjs.com would also be welcome. This will drastically reduce download times(compared to using git) and will make version management easier
bump