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
It is very common scenario to create AWS Lambda functions that rely on some common functionality that can't be installed through npm. In that case, developers use the npm link mechanism in order to include these locally developed node modules.
The current packaging functionality does not take into account these linked modules, probably because they are not listed in the package.json.
Is it possible to package these linked modules in the lambda distribution zip?
The text was updated successfully, but these errors were encountered:
It is very common scenario to create AWS Lambda functions that rely on some common functionality that can't be installed through npm. In that case, developers use the npm link mechanism in order to include these locally developed node modules.
The current packaging functionality does not take into account these linked modules, probably because they are not listed in the package.json.
Is it possible to package these linked modules in the lambda distribution zip?
The text was updated successfully, but these errors were encountered: