chore: migrate monorepo to eslint v9 #17934
Open
Conversation
This file contains 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
which was for Stylus
and simplify it by using mode: auto
which runs quasar prepare, which requires ui package to be built due to logic in vite-plugin removing at least until quasarframework#17935 gets merged
forgot prepare was a special script
Build ResultsJSON API📜 No changes detected. Types📜 No changes detected. |
UI Tests Results 1 files 98 suites 42s ⏱️ Results for commit dae9313. |
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?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
devbranch (orv[X]branch)Other information:
See this and the related issue:
ota-meshi/eslint-plugin-lodash-template#388
I forked it and published it as
@yusufkandemir/eslint-plugin-lodash-template