feat(dev): add option to specifying which paths will be replaced when…#21
Open
panec wants to merge 2 commits intoaem-vite:mainfrom
Open
feat(dev): add option to specifying which paths will be replaced when…#21panec wants to merge 2 commits intoaem-vite:mainfrom
panec wants to merge 2 commits intoaem-vite:mainfrom
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
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.
Add option to specifying which paths will be replaced when injecting vite files
Description
I wanted to control which files (paths) are replaced when I inject vite files. In my current setup I have multiple JS and CSS files but only some of them are present on the page - themes. Currently all vite files are returned but I wanted to be able to cherry pick which paths are replaced with which specific vite files.
Updating code to allow to pass object in Client Lib Expression option. For example
Additional context
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123).