Fixed
Status Update
Comments
mi...@gmail.com <mi...@gmail.com> #2
Have the exact same problem. Following
ab...@gmail.com <ab...@gmail.com> #3
I am also facing similar problem
jb...@gmail.com <jb...@gmail.com> #4
I found a solution !
You add a file named ".npmrc" at the root of your npm project.
This is the content of the file (just 1 line) :
legacy-peer-deps=true
By adding this configuration file, gae will run the legacy peer deps during the build of the deployment.
You add a file named ".npmrc" at the root of your npm project.
This is the content of the file (just 1 line) :
legacy-peer-deps=true
By adding this configuration file, gae will run the legacy peer deps during the build of the deployment.
di...@google.com <di...@google.com> #5
Hello,
I am glad to hear that issue is resolved. Thank you for reaching out.I'm going to close this thread which will no longer be monitored. If you have any further issues please open a new
a....@hiseis.com <a....@hiseis.com> #6
on 21/4/23, google seems changing the policy, and ignoring the legacy-peer-deps=true flag in file .npmrc
je...@doctoride.com <je...@doctoride.com> #7
It is still working on my GAE project (I just pushed a new version) :
* standard environment
* runtime: nodejs16
* standard environment
* runtime: nodejs16
tr...@gmail.com <tr...@gmail.com> #8
Still works on my side
* standard environment
* runtime: nodejs18
* standard environment
* runtime: nodejs18
je...@gmail.com <je...@gmail.com> #9
Still works!
Description
At each GAE deployment (gcloud app deploy), GAE is installing all the dependencies (npm install / npm ci --quiet). At this point everything is normal.
However, since the lastest npm release version (8.11.0), the "npm install" command is failing if the project has conflicts peer dependencies.
Potential solutions :
* Use legacy-peer-deps : There is a configuration to avoid this problem : "npm install --legacy-peer-deps". But I don't find any GAE configurations to configure npm with this command for the build.
* Use an older version of npm : GAE standard use the latest minor version of nodeJs. You can not specify the minor version :
* Delete all the peerDependencies : This project is an Angular SSR Web App project with many different publics dependencies (some of them are not up to date). This is why I have some conflicts peer dependencies. Delete all the peer dependencies would cause other problems in the futur.
Also, I don't want to use a flexible environment, i would like to stay on a standard environment on GAE.
Does anyone has some ideas to help me with this problem ? Thank you very much.