feat(preprocess): check preprocess dependencies for anomalies #767
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
… array, remove .css check as it is too unreliable
Co-authored-by: Bjorn Lu <[email protected]>
Merged
Merged
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.
depending on itself
this is usually a sign for a bad setup/import, see #763
depending on many files
all these files have to be read separately and changing one of them leads to a hot reload of the component. Depending on a few files is ok, but many cause issues.
Messages get added as extra compiler warnings using the
vite-plugin-svelte-preprocess-prefix. This way users can opt to ignore them viaonwarnhook.Are these checks too rigid and do we need FAQ entries and link them in the messages?