-
Notifications
You must be signed in to change notification settings - Fork 3.4k
cli issue #3560
Comments
understood, and confirmed.. digging deeper it appears the last upgrade of our packages was done using a version of npm that has different behaviors, i found several conflicts in our source tree (for example, our react and react-native versions are in conflict, expo-three and three, etc.) i'm able to work around the issue with cli flags to npm: ..but it looks like we'll still need to force upgrade/downgrade packages and run regression tests. fun. Also, thanks for the feedback! 💯 |
|
Run this command |
|
thanks for your help kind man, but it still doesnt work ~ $ npm install --legacy-peer-deps
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! Exit handler never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://github.com/npm/cli/issues>
npm ERR! A complete log of this run can be found in:
npm ERR! /data/data/com.termux/files/home/.npm/_logs/2021-09-13T04_28_58_613Z-debug.log |
by the way, im using termux android for my coding ╮(╯_╰)╭ |
please go on your node.js app and run it there |
your package-lock is old cuz it was created in node v14 |
do they have a node.js app? |
sorry for my dumbness but what do i have to run? |
The text was updated successfully, but these errors were encountered: