[1.x] Differentiate plugin log from Vite log #19
Merged
+1
−1
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.
Hey @ElMassimo! Got a small proposal here for your consideration.
Currently, when the Full Reload plugin performs a reload it logs the following...
This is great.
If I disable the Full Reload plugin and have a dependency loop, which is very common when using something like Tailwind CSS with template files, Vite will output the following when a dependency in said loop is updated...
When seen in combination it makes it harder debug where the issue came from. Was this reload triggered by Full Reload or by Vite? I would like to propose that the console output for this plugin differentiate itself from the logging that Vite itself does.
This is really just a debugging improvement to determine where the issue actually came from.
Thanks again for this fantastic plugin.