Node version stuck at 12.19.0, not configurable via package.json [203594728]

Fixed

Bug

Status Update

No update yet.

Description

ch...@valoraapp.com

created issue #1

Oct 19, 2021 11:06PM

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:
I am trying to update the version of my Nodejs service to ^12.22.1, from >=12.0.0 . I configured the engine version following the instructions here:

https://cloud.google.com/appengine/docs/flexible/nodejs/runtime , which say to put this in my package.json:
```
"engines": {
"node": "YOUR_VERSION"
},
```
(I changed YOUR_VERSION from >=12.0.0 to ^12.22.1)

However when I deploy I get this error:
```
Step #1: error myservicename@0.0.1: The engine "node" is incompatible with this module. Expected version "^12.22.1". Got "12.19.0"
```

What you expected to happen:
I expected the service to start successfully with a newer version of node.

Steps to reproduce:
Deploy an app on App Engine with a flex environment and a node version configured to >=12.0.0, then update the node version to ^12.22.1 in package.json and try to deploy again

Other information (workarounds you have tried, documentation consulted, etc):
I tried updating to other versions of node (14, 16) with no success.

It looks like others are experiencing this problem too

https://www.reddit.com/r/googlecloud/comments/mvmew0/gae_flexible_environment_not_respecting_the_node/

https://stackoverflow.com/questions/69360628/specifying-node-js-version-for-google-cloud-app-engine-flexible

Comments

ch...@valoraapp.com <ch...@valoraapp.com> #2Oct 20, 2021 05:08PM

Hello

Thank you for reaching out to us!

This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through link to learn more about issue trackers. Also, please refer to this Stackoverflow thread regarding resolving the error that you’re getting.

I recommend you to ask the technical questions on Stack Exchange sites which are best suited for this type of questions.

I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.

Thank you

em...@google.com <em...@google.com> #3Oct 22, 2021 02:30PM

Thank you for your report. As you mentioned on your comment the node version is moving to the default one this is mainly to the issue reported here, this has already been reported to the engineering team and they're working on a fix for it.

As a workaround the version "v14.18.0" runs well in App Engine Flex and will be installed properly

ge...@gmail.com <ge...@gmail.com> #4Dec 9, 2021 01:58PM

I tried to specify "engines": { "node": "14.18.0" }, but I still get the error during build:

error @bindr/dev@1.0.0: The engine "node" is incompatible with this module. Expected version "14.18.0". Got "12.19.0"

Is that issue relevant to build environment runtime errors as well?

I also opened a ticket before, which was closed without a solution: https://issuetracker.google.com/issues/202515249

Message last modified on Dec 9, 2021 02:10PM

ge...@gmail.com <ge...@gmail.com> #5Dec 20, 2021 09:41AM

As they confirmed in the issue you linked, our issue is a separate one from that and so a fixed Node version will not solve it.

Therefore I would ask the engineering team for at least a workaround (e.g. updating the default version to at least the latest v12 or providing a Dockerfile that we can use as a custom environment) until this issue gets fixed, because many packages don't support v12.19 anymore and installing older versions can come with serious security vulnerabilities. It's also unacceptable to provide a cloud service that has components not updated for more than a year.

I'm looking forward to your answer.

[Deleted User] <[Deleted User]> #6Jan 13, 2022 05:24AM

Hi,

I am trying to deploy app engine flex with node 14.x version, but app engine throws the error saying "Expected version "14.18.0". Got "12.19.0" " also tried with multiple LTS 14.x versions but app engine keeps throwing the same mentioned error. It seems like app engine flex did not consider the mentioned node version from package.json file and pulls default node js version which is latest 12.19.0 from google's container image registry.

Kindly provide me a solution so that I can proceed with our deployment.

Thanks

[Deleted User] <[Deleted User]> #7Jan 24, 2022 06:13PM

I am also experiencing this issue.

[Deleted User] <[Deleted User]> #8Jan 27, 2022 04:50PM

Have the same issue

pi...@gmail.com <pi...@gmail.com> #9Feb 11, 2022 07:57PM

Same issue for me... Still no news?

ge...@gmail.com <ge...@gmail.com> #10Feb 14, 2022 04:44PM

The only solution so far seems to be to use a custom docker file.

E.g., create a file called Dockerfile in the same directory as your app.yaml file is:

FROM node:16-bullseye

COPY . .

RUN yarn install --non-interactive --frozen-lockfile

ENV NODE_ENV=production
ENV PORT 8080

RUN yarn run gcp-build
RUN rm -Rf node_modules

RUN yarn install --non-interactive --frozen-lockfile --production

CMD yarn start

The specify the runtime in app.yaml.

service: content-server
# Custom runtime required for Node.js > v12.19
# See SO question: https://stackoverflow.com/questions/69360628/specifying-node-js-version-for-google-cloud-app-engine-flexible
runtime: custom
env: flex

...

al...@gmail.com <al...@gmail.com> #11Feb 27, 2022 11:43AM

Also experiencing this issue!

[Deleted User] <[Deleted User]> #12Mar 8, 2022 04:02PM

Bumping this thread as it is still not fixed.
The documentation clearly states "The runtime uses the latest stable release of the version that is specified in your app.yaml file". But this is not true as it is hardcoded to 12.19 for nodejs12. It really is unacceptable this hasn't been fixed yet

Message last modified on Mar 8, 2022 04:03PM

le...@gmail.com <le...@gmail.com> #13Apr 13, 2022 08:00AM

Still not fixed! What's happened as it was working before?
We have 2 instances with the same code and same config, one is working properly, the second one throw the node version error?

gu...@google.com <gu...@google.com> Apr 13, 2022 05:55PM

Assigned to gc...@google.com.

cv...@google.com <cv...@google.com> #14Apr 22, 2022 05:20PM

Hello Team,

Thank you so much for your information and commitment the Product Team is currently working on this you can see more details about this in this post. At this moment there is not an ETA but you can receive updates in this channel.

ta...@gmail.com <ta...@gmail.com> #15Sep 29, 2022 07:14AM

I have the same problem today. Did this have any resolution?

ra...@gmail.com <ra...@gmail.com> #16Oct 20, 2022 06:31PM

Any updates to this? I've tried pinning multiple versions, and nothing works.

pi...@arsen.co <pi...@arsen.co> #17Feb 21, 2023 02:00PM

Up, is there any news on it? Still not working

va...@google.com <va...@google.com> Nov 6, 2023 07:01AM

Reassigned to ku...@google.com.

ku...@google.com <ku...@google.com> #18Nov 8, 2023 07:58AM

Marked as fixed, reassigned to gc...@google.com.

Hello,

I’m pleased to inform you that our product engineering team has resolved the reported issue. Please refer to the GitHub issue for more information and workarounds.

If you encounter any further issues or have any additional concerns, please don't hesitate to create a new issue on the IssueTracker providing a detailed description of your issue.

I will now proceed to close this issue. If you have any other questions or need further assistance, please feel free to let us know.

Thank you!