-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMPORTANT: npm package not up to date #323
Comments
Current version in code is 2.0.0 openfoodfacts-nodejs/package.json Line 3 in c261d98
And version on npm is 0.1.0 Is there a reason the dev branch state hasn't been released? And the related PR not approved? |
@VaiTon should we consider releasing ? |
Because it isn't stable yet, and the main branch is still in develop. Any help is appreciated though! |
@LBF38 in the meantime you can use the git dependency in the package.json https://docs.npmjs.com/cli/v10/configuring-npm/package-json#git-urls-as-dependencies |
That's true ! Completely forgot about that. Thanks for the reminder 🙏 |
I tried with the following
About the argument
It's possible to release a version "2.0.0-alpha.x" or "2.0.0-beta.x". npm will still consider the current version as the latest. To install the unstable package, you will have to use As an example, you can see the |
What
The npm package corresponding to this repo is not up to date to the latest development.
See here for more info.
Steps to reproduce the behavior:
pnpm add openfoodfacts-nodejs
in your terminal (ornpm i ...
node_modules
folderopenfoodfacts-nodejs
package folderrequire
but no IntelliSense.Expected behavior
To have the latest code of this repo in the package.
Screenshots
Platform (Desktop, Mobile, Hunger Games)
Part of
The text was updated successfully, but these errors were encountered: