-
Notifications
You must be signed in to change notification settings - Fork 41
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
Compatible with layers? #48
Comments
similar issue as above. using layers and excluded in package, plugin still tries to find package in node_modules folder and breaks the deployment. |
|
I have the same issuer with layer |
I solved my problem using cont to define path const sharedPath = env.LAYER_PATH || '/opt/nodejs/apiDashgo.js'; const dashgo = require(sharedPath); |
Has this ever been solved? |
Is this plugin compatible with lambda layers?
I'm trying to deploy a package that uses a layer and receiving this error message:
Path must be a string. Received null
Appears to be related to my include of the file in my layer:
const pkg = require('/opt/package1')
The text was updated successfully, but these errors were encountered: