0
217
VistasDeploying node.js to azure web app Via Github Actions, I keep failing my build due to some error that i quoted and screenshot below. Please & Ty
["npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
core-js@3.21.1 postinstall /home/runner/work/team-mario-p2-frontend/team-mario-p2-frontend/node_modules/core-js node -e "try{require('./postinstall')}catch(e){}"
core-js-pure@3.21.1 postinstall /home/runner/work/team-mario-p2-frontend/team-mario-p2-frontend/node_modules/core-js-pure node -e "try{require('./postinstall')}catch(e){}"
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
1 Respuestas
Responde la pregunta0
Most likely your problem is that you're using different npm versions locally and in actions.
If this is the issue, then you can resolve it by specifying a different node version with the setup-node action. For example, specifying node 16 means you'll get npm 8.
Specifying node 12, on the other hand, will lead to npm 6. npm 6 is also what causes lockfile version 1 while npm 8 uses lockfile version 2.
Sample:
uses: actions/setup-node@v3
with:
node-version: 16