Please Add Support for NodeJS 16 #490

iamderrick · 2021-10-27T21:14:04Z

NodeJS 16 entered active long-term support very recently. Can you please add this runtime to the codebuild images?

koooge · 2021-11-23T12:38:07Z

👍

workaround

phases:
  install:
    runtime-versions:
      nodejs: 14
    commands:
      - n 16

- CodeCompile still uses node 14.17.2 - Fix to get nodejs 16 aws/aws-codebuild-docker-images#490 and here https://stackoverflow.com/questions/66590492/aws-codebuild-tsc-error-ts2307-cannot-find-module

nhaynes · 2021-12-30T19:51:28Z

If the images use version managers under the hood, why limit the number of available runtime versions to a static set? Couldn't these images just be updated to pass specific versions on to the underlying version managers?

I imagine this could even be backwards compatible with the existing implementation and require a lot less ongoing maintenance of this repository. And a lot fewer workarounds from CodeBuild users.

Specific versions like this would pass straight thru to the nodejs n version manager:

phases:
  install:
    runtime-versions:
      nodejs: 16.13.1

and the image could still provide "supported" versions like 12, 14, 16:

phases:
  install:
    runtime-versions:
      nodejs: 14

per aws/aws-codebuild-docker-images#490 (comment) error: [Container] 2022/02/10 04:49:30 Phase context status code: YAML_FILE_ERROR Message: Unknown runtime version named '16' of nodejs. This build image has the following versions: 12, 14

(note, available images only supports node12 & 14, but you can ovveride it with a command per aws/aws-codebuild-docker-images#490 (comment) ) from fez-frontend: error: [Container] 2022/02/10 04:49:30 Phase context status code: YAML_FILE_ERROR Message: Unknown runtime version named '16' of nodejs. This build image has the following versions: 12, 14

spencerbeggs · 2022-02-11T16:13:46Z

Just wanted to chime in and mention that I was able to use @koooge workaround to install a specific version of Node.js using CDK. You can see the relevant code in my template repo. Thank you!

chunyang-sph · 2022-04-14T04:34:44Z

waiting for support nodejs version 17

critesjm · 2022-04-19T16:48:03Z

bump! 16 has been in LTS for a while now...

wilhen01 · 2022-05-03T10:33:24Z

Bump. Would be really good to have this...

Chase-Dickerson · 2022-05-18T17:03:02Z

They're getting closer, it seems. NodeJS 16 runtime is now supported for Lambdas. However, it is not yet available for codebuild.

zoellner · 2022-05-23T14:05:52Z

FYI, this seems to work now. docs still not updated but I tried it just now:

  install:
    runtime-versions:
      nodejs: 16



[Container] 2022/05/23 14:01:37 No commands found for phase name: install
--
7 | [Container] 2022/05/23 14:01:37 Processing environment variables
8 | [Container] 2022/05/23 14:01:37 Selecting 'nodejs' runtime version '16' based on manual selections...
9 | [Container] 2022/05/23 14:01:37 Running command echo "Installing Node.js version 16 ..."
10 | Installing Node.js version 16 ...
11 |  
12 | [Container] 2022/05/23 14:01:37 Running command n $NODE_16_VERSION
13 | copying : node/16.15.0
14 | installed : v16.15.0 (with npm 8.5.5)

Edit: don't recommend this yet. it only works sometimes and seems to be random chance if the build server supports it yet or not

mneil · 2022-05-23T16:42:39Z

Using a version manager isn't a viable solution to picking a version.

It increases already long build times / startup for an already slow service.
I'm paying for build times. See problem 1
Builds running in a VPC without an internet connection cannot pull and build new versions of node

AMI2022 isn't supported on codebuild. AMI2 is dead along with CentOS. Ubuntu images do not have latest software available even a year after it's been released. Please support your own products.

DylanVann · 2022-05-23T18:40:33Z

Saw that Lambda supports Node 16 now, as of 10 days ago.
Created PR to update Lamdba runtime, updated the CodeBuild runtime at the same time.
PR runs on CodeBuild, uses Node 16 as mentioned Please Add Support for NodeJS 16 #490 (comment).
Merged PR.
Other PRs are now failing saying Unknown runtime version named '16' of nodejs.

So it seems that it isn't exactly fully rolled out. Very unfortunate it's only intermittently working, builds should be reproducible.

DylanVann · 2022-05-23T18:48:43Z

I also get 'nodejs16.x' runtime is not supported as a Lambda error when downgrading just CodeBuild.

Is there some way to clear the pool of build machines we're using and just get ones that support Node 16?

jpduckwo · 2022-05-24T06:03:35Z

Tried in region ap-southeast-2... nodejs: 16 isn't available yet

arturoribessanz · 2022-05-24T09:31:15Z

Yesterday morning it was available. At night and now it is not. Looks like they are having some issues updating the version.

maheshsamudra · 2022-05-25T04:26:10Z

Yesterday morning it was available. At night and now it is not. Looks like they are having some issues updating the version.

Finally... it's good to know that they are working on it! I was checking https://docs.aws.amazon.com/codebuild/latest/userguide/available-runtimes.html#linux-runtimes every week to see if it's available.

recs182 · 2022-05-25T18:32:27Z

eu-central-1 also does not support it yet... really disappointed since the application won't build at pipelines and therefore blocks the use of node 16 and npm 8.

brazilianbytes · 2022-05-25T20:09:50Z

+1. It's a nice feature because Node 12 will go EOF at April 2022. AWS Lambda already have Node 16 available.

jcuna · 2022-05-30T20:45:59Z

This is pressing. We went through the deal of upgrading lambdas to 16 and we use codebuild to build our lambdas. Hope there's a fix soon.

arturoribessanz · 2022-05-31T05:33:42Z

+1

workaround

phases:
  install:
    runtime-versions:
      nodejs: 14
    commands:
      - n 16

This workaround works well and does not add a lot of time to the build process.

h5aaimtron · 2022-06-02T21:24:46Z

nodejs: latest is defaulting back to v12.22.2 again. It was pulling 14+ for the last few months.

jpduckwo · 2022-06-02T22:48:15Z

nodejs: latest is defaulting back to v12.22.2 again. It was pulling 14+ for the last few months.

I'm sceptical :) What region, and what is your build config?

umertauheed · 2022-06-05T17:07:57Z

nodejs: latest is defaulting back to v12.22.2 again. It was pulling 14+ for the last few months.

having same issue for few days.

nodejs: latest is defaulting back to v12.22.2 again. It was pulling 14+ for the last few months.

I'm sceptical :) What region, and what is your build config?

region: Singapore

HansFalkenberg-Visma · 2022-06-07T12:17:32Z

It'd be great if codebuild could commit to getting the next LTS of node out earlier, like Lambda has (almost) promised.

We recognize that customers have been waiting for some time for this runtime release. We hear your feedback and plan to release the next Node.js runtime version in a timelier manner.

https://aws.amazon.com/blogs/compute/node-js-16-x-runtime-now-available-in-aws-lambda/

monigala · 2022-06-10T17:51:37Z

👍

workaround

phases:
  install:
    runtime-versions:
      nodejs: 14
    commands:
      - n 16

After buildspec completes, the AWS Lambda displays Runtime Node.js 14.x. So its confusing. It's built with v16 but runs on v14?

benton · 2022-06-14T21:14:18Z

The production images built from this repo are referenced in the AWS CDK as, aws_cdk.aws_codebuild.LinuxBuildImage

a new version of the AWS CDK was released today that has broken CDK pipelines because it was not tested against Node 12 (or because Node 14 and/or 16 are not included in these images, depending your perspective).

Please release newer images with more recent, production-ready versions of NodeJS as soon as possible, thanks.

mbsimonovic · 2022-06-22T12:58:52Z

us-east-1:

[Container] 2022/06/22 12:56:52 Unknown runtime version named '16' of nodejs. This build image has the following versions: 12, 14
10

subinataws · 2022-07-01T21:05:54Z

Addressed in https://github.com/aws/aws-codebuild-docker-images/releases/tag/22.06.30

HansFalkenberg-Visma · 2022-07-05T07:40:20Z

Thanks for getting this out. However, the documentation still says nodejs 14 is the latest available:
https://docs.aws.amazon.com/codebuild/latest/userguide/runtime-versions.html
https://docs.aws.amazon.com/codebuild/latest/userguide/available-runtimes.html
Update 2022-07-14: documentation has nodejs 16 now

Also, anyone using CDK will have to wait just a little longer, if they don't want to use workarounds: aws/aws-cdk#20960

maheshsamudra · 2022-09-01T14:32:01Z

Nope. I moved back to Node 14 in standard5:0. This is not reliable yet. What's up with AWS seriously?

…

On Thu, Sep 1, 2022 at 1:40 PM nandita121189 ***@***.***> wrote: I'm still getting the below error Phase context status code: YAML_FILE_ERROR Message: Unknown runtime version named '16' of nodejs. This build image has the following versions: 10, 12 The environment used for codebuild is as follows: Environment: Type: LINUX_CONTAINER Image: aws/codebuild/standard:6.0 ComputeType: BUILD_GENERAL1_SMALL Buildspec versions needed install: runtime-versions: python: 3.8 nodejs: 16 Region is us-west-2 Is it working for someone? — Reply to this email directly, view it on GitHub <#490 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFYVLDNKG7SSLK57JE3G43DV4BQIPANCNFSM5G3KBAEQ> . You are receiving this because you commented.Message ID: ***@***.***>

monigala · 2022-09-01T15:27:32Z

We are using node16 in the "*us-east-1*" region. The attached AWS article indicates it's available in all regions. *cloudformation template* Type: LINUX_CONTAINER Image: aws/codebuild/standard:6.0 ComputeType: BUILD_GENERAL1_SMALL *serverless.yml* provider: name: aws runtime: nodejs16.x An alternative is to use a custom Image that you build yourself. We used a private ECR Image with node16 prior to this option being available. *helpful articles* https://aws.amazon.com/about-aws/whats-new/2022/05/aws-lambda-adds-support-node-js-16/ https://docs.aws.amazon.com/lambda/latest/dg/nodejs-image.html On Thu, Sep 1, 2022 at 7:32 AM Mahesh Samudra ***@***.***> wrote:

…

Nope. I moved back to Node 14 in standard5:0. This is not reliable yet. What's up with AWS seriously? On Thu, Sep 1, 2022 at 1:40 PM nandita121189 ***@***.***> wrote: > I'm still getting the below error > > Phase context status code: YAML_FILE_ERROR Message: Unknown runtime version named '16' of nodejs. This build image has the following versions: 10, 12 > > The environment used for codebuild is as follows: > > Environment: > Type: LINUX_CONTAINER > Image: aws/codebuild/standard:6.0 > ComputeType: BUILD_GENERAL1_SMALL > > Buildspec versions needed > > > install: > runtime-versions: > python: 3.8 > nodejs: 16 > > Region is us-west-2 > > Is it working for someone? > > — > Reply to this email directly, view it on GitHub > < #490 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AFYVLDNKG7SSLK57JE3G43DV4BQIPANCNFSM5G3KBAEQ > > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#490 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACFLO27VIKOUGQCWWY3SWTTV4C47BANCNFSM5G3KBAEQ> . You are receiving this because you commented.Message ID: ***@***.***>

nociza · 2022-09-10T08:25:35Z

It seems that the aarch64 containers only support up to 12, which really should be updated by now.
Message: Unknown runtime version named '16' of nodejs. This build image has the following versions: 10, 12

cihan-paytrail · 2022-09-26T09:14:35Z

I resolved this issue by updating the CodeBuild Linux image from the default 5.0 to 6.0.

E.g. with TypeScript & AWS CDK:

new PipelineProject(scope, `my-build`, {
  environment: {
    buildImage: LinuxBuildImage.STANDARD_6_0,
  }
});

ilyakonrad · 2022-10-31T13:06:51Z

Year later it is still not supported?

dls314 · 2022-10-31T14:02:19Z

Year later it is still not supported?

Supported #490 (comment)

ilyakonrad · 2022-10-31T14:04:52Z

Year later it is still not supported?

Supported #490 (comment)

I mean nodejs: 16 didn't work today, should I use the full version name?

thiagosanches · 2022-10-31T16:40:35Z

It's not working yet:

N1kell · 2022-11-04T12:02:28Z

It's not working yet:

For me switching "Current environment image" to aws/codebuild/standard:6.0 solved the issue

GabrielDelepine · 2023-01-02T11:15:58Z

The available runtimes are listed in the definition of the docker images provided by CodeBuild

https://docs.aws.amazon.com/en_us/codebuild/latest/userguide/build-env-ref-available.html

For instance

aws/codebuild/amazonlinux2-aarch64-standard:1.0 supports nodejs 8, 10 and 12
aws/codebuild/amazonlinux2-aarch64-standard:2.0 supports nodejs 10 and 12
aws/codebuild/amazonlinux2-x86_64-standard:3.0 supports nodejs 10 and 12
aws/codebuild/amazonlinux2-x86_64-standard:4.0 supports nodejs 16
aws/codebuild/standard:6.0 supports nodejs 16

joebowbeer · 2023-01-19T10:49:09Z

@koooge wrote:

workaround

phases:
  install:
    runtime-versions:
      nodejs: 14
    commands:
      - n 16

In case it's not clear, this same technique can be used to install nodejs 18 on aws/codebuild/standard:5.0

phases:
  install:
    runtime-versions:
      nodejs: 14
    commands:
      - n 18

jezhodges mentioned this issue Nov 3, 2021

Add Node 16 LTS runtime #494

Closed

subinataws added the version update label Nov 8, 2021

subinataws mentioned this issue Jan 24, 2022

Support for nodejs version 16 & npm 8 #510

Closed

wilhen01 mentioned this issue May 3, 2022

Please Update Node 14 #525

Closed

aws deleted a comment from alex-schwartzman-at-stratify Jun 17, 2022

indrora mentioned this issue Jun 23, 2022

SyntaxError: Unexpected token '?' on Amazon Linux 2 CodeBuild images (Node 14 required starting at 2.28.0) aws/aws-cdk#20739

Closed

This was referenced Jun 30, 2022

Release standard:6.0 and amazonlinux2-x86_64-standard:4.0 #542

Closed

Release standard:6.0 and amazonlinux2-x86_64-standard:4.0 #543

Merged

subinataws closed this as completed Jul 1, 2022

aws deleted a comment from MoMannn Jul 4, 2022

chalimbu pushed a commit to juanpa-dev/bike_microservices that referenced this issue Oct 28, 2022

node 16 workaround aws/aws-codebuild-docker-images#490

cc7837d

HaaLeo mentioned this issue Nov 15, 2022

Add support for Node 18 #580

Closed

justinmk3 mentioned this issue Jan 30, 2023

deps: update vscode-test aws/aws-toolkit-vscode#3136

Merged

pvcresin mentioned this issue Sep 12, 2023

Add support for Node 20 #631

Closed

Please Add Support for NodeJS 16 #490

Please Add Support for NodeJS 16 #490

Comments

iamderrick commented Oct 27, 2021

koooge commented Nov 23, 2021

nhaynes commented Dec 30, 2021

spencerbeggs commented Feb 11, 2022

chunyang-sph commented Apr 14, 2022

critesjm commented Apr 19, 2022

wilhen01 commented May 3, 2022

Chase-Dickerson commented May 18, 2022

zoellner commented May 23, 2022 • edited Loading

mneil commented May 23, 2022

DylanVann commented May 23, 2022

DylanVann commented May 23, 2022

jpduckwo commented May 24, 2022

arturoribessanz commented May 24, 2022

maheshsamudra commented May 25, 2022

recs182 commented May 25, 2022

brazilianbytes commented May 25, 2022

jcuna commented May 30, 2022

arturoribessanz commented May 31, 2022

h5aaimtron commented Jun 2, 2022

jpduckwo commented Jun 2, 2022 • edited Loading

umertauheed commented Jun 5, 2022 • edited Loading

HansFalkenberg-Visma commented Jun 7, 2022

monigala commented Jun 10, 2022

benton commented Jun 14, 2022

mbsimonovic commented Jun 22, 2022

subinataws commented Jul 1, 2022

HansFalkenberg-Visma commented Jul 5, 2022 • edited Loading

maheshsamudra commented Sep 1, 2022 via email

monigala commented Sep 1, 2022 via email

nociza commented Sep 10, 2022

cihan-paytrail commented Sep 26, 2022 • edited Loading

ilyakonrad commented Oct 31, 2022

dls314 commented Oct 31, 2022

ilyakonrad commented Oct 31, 2022

thiagosanches commented Oct 31, 2022

N1kell commented Nov 4, 2022 • edited Loading

GabrielDelepine commented Jan 2, 2023 • edited Loading

joebowbeer commented Jan 19, 2023

zoellner commented May 23, 2022 •

edited

Loading

jpduckwo commented Jun 2, 2022 •

edited

Loading

umertauheed commented Jun 5, 2022 •

edited

Loading

HansFalkenberg-Visma commented Jul 5, 2022 •

edited

Loading

cihan-paytrail commented Sep 26, 2022 •

edited

Loading

N1kell commented Nov 4, 2022 •

edited

Loading

GabrielDelepine commented Jan 2, 2023 •

edited

Loading