-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
BuildMethod: esbuild
does not include bundled files
#7143
Labels
Comments
jghaines
added
the
stage/needs-triage
Automatically applied to new issues and PRs, indicating they haven't been looked at.
label
Jun 7, 2024
Hi @jghaines Thanks for the detailed reproduction steps! I was able to reproduce the issue and will mark it as a bug for the team to prioritize a fix |
sidhujus
added
type/bug
area/build
sam build command
area/esbuild
and removed
stage/needs-triage
Automatically applied to new issues and PRs, indicating they haven't been looked at.
labels
Jun 12, 2024
aws/aws-lambda-builders#516 Looking into it a bit further this seems like it falls under this feature request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Some npm packages, or lambda source modules, include bundled files.
When using
Metadata.BuildMethod: esbuild
these bundled files are not included in the deployment packageWhen using default javascript (without esbuild) these bundled files are correctly included.
Steps to reproduce:
The bug is revealed when using the following nodejs20.x sam-app-templates:
To each templated-app I add the npm module errorhandler which depends upon bundled
./public/*
files to initialise.Observed result:
Expected result:
Repeating the above steps with the default javascript app-template (no typescript/esbuild) works as expected:
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
Darwin Macbook2022.local 23.5.0 Darwin Kernel Version 23.5.0: Wed May 1 20:19:05 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8112 arm64
sam --version
: SAM CLI, version 1.118.0The text was updated successfully, but these errors were encountered: