Closed favna closed 2 months ago
Due to backporting features to 1.4.9 running npm install chrono-node will currently install v1.4.9 because it's marked as latest on npm: https://www.npmjs.com/package/chrono-node
npm install chrono-node
latest
The fix is to run npm dist-tag to move the latest tag, see https://docs.npmjs.com/cli/v8/commands/npm-dist-tag/
npm dist-tag
As for GitHub, the 1.4.9 release should be edited removing the "mark as latest" checkbox and then do the same in reverse for latest v2.
Ops. Sorry for the problem.
When releasing 1.4.9, I originally planned to release 2.7.7 on the same day. However, I didn't complete the later.
This should be fixed after 2.7.7 this week.
Due to backporting features to 1.4.9 running
npm install chrono-node
will currently install v1.4.9 because it's marked aslatest
on npm: https://www.npmjs.com/package/chrono-nodeThe fix is to run
npm dist-tag
to move the latest tag, see https://docs.npmjs.com/cli/v8/commands/npm-dist-tag/As for GitHub, the 1.4.9 release should be edited removing the "mark as latest" checkbox and then do the same in reverse for latest v2.