-
Notifications
You must be signed in to change notification settings - Fork 141
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
Esbuild nodejs builder #252
Conversation
… remove garbage lockfile left by npm 7
… package.json options
@gojko Hi there, is there any update on this? This would be such a great feature for CDK + Typescript Lambda with SAM. 🙏 |
@mgrandis or other aws people is there any forcast / outline / perspective to get this merged soon? |
@mgrandis Is there a possibility to get some more information if this PR will be reviewed in the near future? |
Just pinging more AWS folks to see what do we need to make this happen. 🙏 |
Yes! So sorry for the late reply! |
@mgrandis any updates? There are conflicts now as this is ready for almost 3 months now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments to kick things off.
Can you fix the conflicts? We recently released ARM support which made some significant changes to the code base.
Thanks.
@@ -80,19 +81,23 @@ class NodejsNpmInstallAction(BaseAction): | |||
DESCRIPTION = "Installing dependencies from NPM" | |||
PURPOSE = Purpose.RESOLVE_DEPENDENCIES | |||
|
|||
def __init__(self, artifacts_dir, subprocess_npm): | |||
def __init__(self, artifacts_dir, subprocess_npm, mode="--production"): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we pass a flag on which we act upon in execute
instead of the value that we use.
This way if the value was to change or the way we pass the value to NPM was to change, we would only have to update execute
.
The way this is currently done also allows passing any arbitrary value to NPM which I think is not something we want to allow.
:raises lambda_builders.actions.ActionFailedError: when esbuild packaging fails | ||
""" | ||
|
||
if 'entry_points' not in self.bundler_config: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use double quotes on our projects "
for strings.
Please ensure you have run make pr
.
@mgrandis I've lost interest in this and migrated to another solution since this was so long in the pipeline. If you think it's still worth merging, perhaps just take over? |
Got it, thanks @gojko! |
Closing in favor of #307 |
Issue #, if available:
Solves the following issues or makes them obsolete
Description of changes:
Support for ESBuild bundler running as part of the Nodejs NPM workflow, providing the following benefits:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.