Support forceExclude to exclude dependencies #248
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:
Closes #247
How did you implement it:
The configuration now allows for a
forceExclude
array besides theforceInclude
array. All modules specified will be forcefully excluded, even if they appear as production dependencies. If the excluded dependency includes a peer dependency, this has to be excluded manually because the peer is still required, even if the excluded dependency is drawn from somewhere else.Sample:
The precedence is
exclude -> include
, i.e. if a module appears in include as well as in exclude, it will be excluded (exclude wins).How can we verify it:
Just use a configuration as in the sample above, do a
serverless package
and check the zip files created in.serverless
.Todos:
Is this ready for review?: YES
Is it a breaking change?: NO