Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Upgrading to 4.0.0 appears to break lambdas using docker

Aberta
  • Algo errado?
#170 15 comentários 6 reações 1 responsável Ver no GitHub

@godcrampy já está trabalhando nisso.

Desde 11/12/2025.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

bug

I had been using

RUN npm install -g aws-lambda-ric

Which is on me for not pinning it to a specific version, but with this after the 4.0.0 release on a new build of an image the lambda will no longer start.

2025-12-06T02:12:47.652Z | npm error could not determine executable to run
-- | --
  | 2025-12-06T02:12:47.653Z | npm error A complete log of this run can be found in: /tmp/.npm/_logs/2025-12-06T02_12_46_306Z-debug-0.log
  | 2025-12-06T02:12:47.664Z | INIT_REPORT Init Duration: 1421.03 ms Phase: init Status: error Error Type: Runtime.ExitError

Pinning to 3.3.0 allows our service to run.

RUN npm install -g [email protected]

This is across multiple projects for separate company stacks I am seeing this. I've pinned to 3.3.0 across the board.

This is running with node:24 as a base image, and had experienced with a node:23 deployment.

Here is an example of what is being used for the entrypoint with aws-lambda-ric:

ENTRYPOINT ["/usr/local/bin/npx", "aws-lambda-ric"]
CMD ["lib/serverless/lambda/lambda.handler"]

Noting again that after pinning the lambdas work as expected.

This is too similar to the pattern shown here, where the version is unpinned:

https://github.com/aws/aws-lambda-nodejs-runtime-interface-client/blob/a4560c87426fa0a34756296a30d7add1388e575c/README.md?plain=1#L102

Linguagem predominante
TypeScript
Estrelas
224
Forks
60
Merge médio
26min
PRs com merge (30d)
2

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de aws/aws-lambda-nodejs-runtime-interface-client

Todas as issues de aws/aws-lambda-nodejs-runtime-interface-client

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.