Feat: aws-nodejs-typescript template improvements #6904
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What did you implement
Better defaults and performance improvements for the
aws-nodejs-typescript
template.Including:
I left out the eslint setup as I didn't want to enforce a specific opinion and also to keep consistent with the other aws-nodejs template
Here are the build comparisons for the typical created app via the template, before this change and after.. The gains are even much more significant in a real world projects with more dependencies and files.
Before:

After:

aws-nodejs-typescript template
Closes #6874
How can we verify it
use
sls create -t aws-nodejs-typescript
or manually go to the template, run
npm install
, then runsls webpack
Is this ready for review?: YES
Is it a breaking change?: NO