-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Migrate package-lock.json file to version 2 #105
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Hey , can I work on this |
this one is not needed anymore |
Reason/Context
Parser-JS requires now Node.js 14 and npm7 or higher.
This means
package-lock.json
version should be always set to2
.Description
In order to unify development requirements, I suggest all repositories to stick with that requirements. In order to do that, the following is needed:
package-lock.json
to version2
. This is automatically done when runningnpm install
if the npm version used is 7 or higher.Related:
package-lock.json
is created withv2
.github#177The text was updated successfully, but these errors were encountered: