-
Notifications
You must be signed in to change notification settings - Fork 0
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
adapt sea-map run-scripts for npm v7+ #143
Comments
We support npm v6, but not yet v7+, see #143. As such, v5 expects package-lock.json v1.
When might we need to address this? @wu-lee |
I've needed to bump the version of node in use to a recent one (16.*, i.e. Therefore, I've run into this problem again. But this time I've found a work-around: use Fix applied in 4d90200 |
Oh, the map apps will also need to use a deploy script included in mykomap, that works around the problem. But then to use mykomap they will need various alterations along with this. |
The NPM maintainers, in their wisdom, have decided to remove a feature we use in our run-scripts for building and deploying. As such, we can't use versions of NPM newer than 6 (7 or higher) until we find a way around this missing feature.
See:
npm/cli#2452 (comment)
npm/rfcs#305
The text was updated successfully, but these errors were encountered: