Switch to Webpack #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Member
| Wow. This is great. Thanks so much. I am back in office Monday. I will revise it then. |
lmajano reviewed Jun 28, 2023
lmajano reviewed Jun 28, 2023
Member
| Reviewed, please review the questions. Thanks |
Member
| Thanks so much for assisting. Love it |
Contributor Author
| My pleasure |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
I try to update this extension to use webpack instead of current build.
Advantages are:
Also, I update dependencies, remove unused imports and remove unused VS Code Test Task
*NOTE:
This PR invalidates this PR (#23) because now, Webpack and some babel plugins can handle lodash and make it slim by changing the imports.
But if we don't want Webpack, my old PR is still valid