Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Official docs still recommend obsolete @nx/aws-lambda, which is now unmaintained and doesn't work #23520

Closed
1 of 4 tasks
masonmark opened this issue May 19, 2024 · 0 comments · Fixed by #23971
Closed
1 of 4 tasks
Assignees

Comments

@masonmark
Copy link

Documentation issue

  • Reporting a typo
  • Reporting a documentation bug
  • Documentation improvement
  • Documentation feedback

Is there a specific documentation page you are reporting?

https://nx.dev/recipes/node/node-aws-lambda

Additional context or description

This page looks current at first glance, but it is based on @nx/aws-lambda which is now unmaintained, and also doesn't work.

So everything I did following this tutorial was a waste of time. It's not that long, but trying to use that obsolete plugin also led to cryptic npm install errors like:

npm ERR! Error: dlopen(/Volumes/ACME/ucm-hopscotch-api/.nx/cache/18.3.5-nx.darwin-arm64.node, 0x0001): tried: '/Volumes/ACME/ucm-hopscotch-api/.nx/cache/18.3.5-nx.darwin-arm64.node' (code signature invalid in <2ED4CDDA-275E-30B4-ACF0-E00AC37DB0B7> '/Volumes/ACME/ucm-hopscotch-api/.nx/cache/18.3.5-nx.darwin-arm64.node' (errno=85) sliceOffset=0x00000000, codeBlobOffset=0x005E3690, codeBlobSize=0x0000BCF8), '/System/Volumes/Preboot/Cryptexes/OS/Volumes/ACME/ucm-hopscotch-api/.nx/cache/18.3.5-nx.darwin-arm64.node' (no such file), '/Volumes/ACME/ucm-hopscotch-api/.nx/cache/18.3.5-nx.darwin-arm64.node' (code signature invalid in <2ED4CDDA-275E-30B4-ACF0-E00AC37DB0B7> '/Volumes/ACME/ucm-hopscotch-api/.nx/cache/18.3.5-nx.darwin-arm64.node' (errno=85) sliceOffset=0x00000000, codeBlobOffset=0x005E3690, codeBlobSize=0x0000BCF8)
npm ERR!     at Module._extensions..node (node:internal/modules/cjs/loader:1473:18)
npm ERR!     at Module.load (node:internal/modules/cjs/loader:1207:32)
npm ERR!     at Module._load (node:internal/modules/cjs/loader:1023:12)
npm ERR!     at Module._load (/Volumes/ACME/ucm-hopscotch-api/node_modules/@nx/esbuild/node_modules/nx/src/native/index.js:58:27)
npm ERR!     at Module.require (node:internal/modules/cjs/loader:1235:19)
npm ERR!     at require (node:internal/modules/helpers:176:18)
npm ERR!     at Object.<anonymous> (/Volumes/ACME/ucm-hopscotch-api/node_modules/@nx/esbuild/node_modules/nx/src/native/native-bindings.js:135:29)
npm ERR!     at Module._compile (node:internal/modules/cjs/loader:1376:14)
npm ERR!     at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
npm ERR!     at Module.load (node:internal/modules/cjs/loader:1207:32) {
npm ERR!   code: 'ERR_DLOPEN_FAILED'
npm ERR! }
npm ERR! 
npm ERR! Node.js v20.10.0

It was only through debugging those errors that I finally realized "oh, this package is obsolete and doesn't work anymore".

I think this page should be removed, or at the very least have a header at the top saying "OBSOLETE: For historical reference only" or something like that. (The same applies to any documentation, and ideally official blog posts, too, that references any of the plugins that were recently obsoleted, like @nx/deno, etc.)

@ndcunningham ndcunningham self-assigned this May 21, 2024
ndcunningham added a commit that referenced this issue May 21, 2024
Adds deprecation message for `@nx/aws-lambda` since the module is
deprecated and unmaintained.

Ref: https://www.npmjs.com/package/@nx/aws-lambda

closes: #23520
FrozenPandaz pushed a commit that referenced this issue May 21, 2024
Adds deprecation message for `@nx/aws-lambda` since the module is
deprecated and unmaintained.

Ref: https://www.npmjs.com/package/@nx/aws-lambda

closes: #23520
(cherry picked from commit 992ae85)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants