feat: created dynamic config based on env variables #194
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.
Problem:
We are maintaining two separate config for generating output files. In future we might want to have more of the code which we want to bundle slightly differently. In that scenario, creating new configs is not a scalable solution.
Solution:
Making our rollup config more dynamic.
We get rid of
sw_rollup.config.js
in favour of just one config. We segregate the build by passingMODE
env variable.Test:
I have deleted the generated files in the repository and re-generated it with the new config. No extra changes were commited and no extra files were changed.