init creates a new package.json with an older version
See original GitHub issueHello!
I was trying this out today, and found this behavior confusing:
- Create a new package.json in an empty directory
- Run
yarn add --dev style-dictionary
- get latest version 2.10.0 - Run
yarn run style-dictionary init complete
- the package.json gets templated value:
...
"devDependencies": {
"style-dictionary": "2.9.0"
}
...
I would expect that the generated template match the version installed - unless this is some other behavior?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
npm-init
npm -init. Create a package.json file. Select CLI Version: ... If you want npm to use the latest version, or another specific version...
Read more >npm WARN old lockfile The package-lock.json file was ...
Run npm install --package-lock-only (with the newer version of npm ) to regenerate a package-lock.json . Commit the updated version of package- ...
Read more >[BUG] npm install doesn't use newer tagged version if ... - GitHub
json has reference to older version. If I run npm install with npm@6 the package-lock.json gets updated with latest versions. however, if I...
Read more >package.json Quick Start Guide | phoenixNAP KB
When releasing a new package version, increment: ... npm init, Creates a new package.json file with elementary properties.
Read more >Creating a package.json with npm - LearnHowToProgram.com
This effectively means we can copy/paste a package.json file from another project instead of initializing a new package.json file and manually adding ...
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
We have a pre-version script that should bump up all the version numbers of the examples, but it might be broken… If we moved the repository to a monorepo with each example as its own package then I think this could be handled nicer without a custom script… Maybe something to look in to.
Fixed this in #755