Repository navigation
Conversation
Contributor
|
✅ Staging deployment successful! Preview: https://viteplus-staging.void.app/ |
fengmk2
force-pushed
the
fix/migrate-oxlint-extends
branch
from
October 17, 2026 17:07
bf0e041 to
3b7e402
Compare
fengmk2
force-pushed
the
fix/migrate-oxlint-extends
branch
from
October 18, 2026 03:58
0877f9f to
cac98a4
Compare
This branch has not been deployed
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
1 participant
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.
vp migratecopies JSONextendspaths intolint.extends, butvp lintrequires config objects.The migrator now creates shared TypeScript configs and imports them, including nested inheritance. All migrated consumers, including the owning workspace, import the same module. Shared rule edits apply to every consumer. Migration defaults stay in each workspace's local
lintblock. Rule order, severities, overrides, and explicit options remain intact.The owner references its shared
ignorePatternsat the top level. Other consumers keep their own exclusions. Plugin declarations stay in their original config or override. Relative plugin paths resolve fromimport.meta.url. Original shared JSON files remain available to other consumers.Conflicts or unsupported configs leave the original JSON in place with a warning. Workspace cleanup waits until all migration outcomes are known. Each workspace must complete its own merge before cleanup can remove its JSON path, even when multiple symlinks share a source. Cleanup retains the transitive JSON dependencies of preserved consumers and symlink targets.
Fixes #3089