You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many projects depend on the aws-lambda package, assuming you need it to use imports from the aws-lambda path.
This isn't true since aws make that available internally at runtime.
The package is actually an unrelated cli used to deploy lambdas, and has no effect in most projects using it.
We could probably help out here by:
adding this to the depend eslint plugin
contributing to larger open source consumers of the package to remove the dependency (where it isn't used)
This will help spread the knowledge that you don't actually need the package to write lambdas. Of course, it'll also reduce unnecessary npm downloads too
The text was updated successfully, but these errors were encountered:
Many projects depend on the
aws-lambda
package, assuming you need it to use imports from the aws-lambda path.This isn't true since aws make that available internally at runtime.
The package is actually an unrelated cli used to deploy lambdas, and has no effect in most projects using it.
We could probably help out here by:
depend
eslint pluginThis will help spread the knowledge that you don't actually need the package to write lambdas. Of course, it'll also reduce unnecessary npm downloads too
The text was updated successfully, but these errors were encountered: