Comments (3)
Hi @Cupprum thank you for taking the time to open this issue.
After taking a look at the dependencies that you have listed, and that are mentioned in the warnings emitted when configuring the local development environment it appears that two out of three of these dependencies are transitive dependencies (aka brought in by some of our dependencies) and that are used only in the development environment.
As you can see from our package-lock.json
file, both @npmcli/move-file
and querystring
are not direct dependencies:
@npmcli/move-file
is brought into the development environment of the project vialerna > @npmcli/run-script> node-gyp > make-fetch-happen > cacache
querystring
is brought into the development environment of the project viaaws-sdk
Given that these are transitive dependencies of which we don't have direct control, I would recommend you to open an issue under the repositories of the project that list them directly as dependency - in this case lerna
and aws-sdk
respectively - to ask them to move to the newer versions.
The third dependency @aws-sdk/util-base64-node
is used directly by the Idempotency and Parameters utility and has been left there intentionally. While the package has been marked as deprecated by the AWS SDK for JavaScript team, this is only due to a name change (@aws-sdk/util-base64
).
The reason why we haven't moved our utilities to the new module is because some of the AWS Lambda managed runtimes for Node.js still bundle the older package (the one called @aws-sdk/util-base64-node
) instead of the new one. Using the new one would require all customers using these two Powertools utilities to make sure that the new version (@aws-sdk/util-base64
) is bundled or otherwise present in the Lambda execution environment.
We have noticed this a few months ago and looked at both the old and new package and the implementation has remained the same, so in an effort to offer a low friction adoption and usage for our customers we have opted to remain to the older one for the time being.
As already mentioned, the @npmcli/move-file
and querystring
are not used in the Powertools utilities that are published on npm and that eventually end up in your Lambda functions. The other dependency (@aws-sdk/util-base64-node
) has been intentionally left as-is as explained above and we will continue to periodically check the Lambda managed runtime and update to @aws-sdk/util-base64
when it's safe to do so.
With the above in mind I'll be closing this issue and thank you again for opening the issue and for giving us the chance to document these warnings in this thread.
from aws-lambda-powertools-typescript.
⚠️ COMMENT VISIBILITY WARNING ⚠️
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
from aws-lambda-powertools-typescript.
Thank you and i very much appreciate the transparency.
from aws-lambda-powertools-typescript.
Related Issues (20)
- Docs: typos in tracer docs HOT 1
- Maintenance: temporarily remove README from jsmespath typedoc HOT 1
- Feature request: add safeParse option HOT 3
- Feature request: JMESPath lexer HOT 1
- Feature request: JMESPath built-in functions HOT 2
- Feature request: JMESPath powertools functions HOT 2
- Feature request: JMESPath expression class and utilities HOT 2
- Feature request: JMESPath tree interpreter HOT 1
- Feature request: JMESPath abstract syntax tree (AST) HOT 2
- Feature request: JMESPath parser HOT 2
- Maintenance: drop support for Node.js 16 HOT 5
- Maintenance: v1 enters maintenance mode, scheduled end-of-life
- Maintenance: update versioning & banner for v2 release HOT 1
- Bug: private class fields transformed incorrectly in ESM HOT 2
- Bug: unable to use Lambda Layer with ESM bundles HOT 2
- Maintenance: remove a dependency to deprecated library `@aws-sdk/util-base64-node` HOT 3
- Bug: Exception instead of warning when log level doesn't match AWS log level HOT 5
- Maintenance: reach 100% JMESPath test coverage & spec compliance HOT 2
- Maintenance: type `exports` in Parameters & Idempotency pkgs are incorrect HOT 7
- Bug: Dynamic require error with ESM functions HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aws-lambda-powertools-typescript.