feat(cli-service): use "filenameHashing" option when building wc and wc-async #6538
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
sterashima78 force-pushed the feature/use-filename-hashing-when-building-wc branch from 5babab4 to dc5ea31 Compare | CI |
| Great PR, cant wait for it to be merged ! |
| Any update on this? Really looking forward to this. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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 kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information:
Now, building webcomponents ignore
filenameHashingoption.This PR make building webcomponents using
filenameHashingoption.Becouse default
filenameHashingoption value istrue, This is breaking change.Related issue: #5438