build(deps-dev): move the eslint config packages to the @myparcel-dev scope - #219
Open
FreekVR wants to merge 5 commits into
Open
build(deps-dev): move the eslint config packages to the @myparcel-dev scope#219FreekVR wants to merge 5 commits into
FreekVR wants to merge 5 commits into
Conversation
✅ Deploy Preview for myparcel-developer-portal ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
… scope Moves the eslint config references from @myparcel-eslint to @myparcel-dev. The @myparcel-eslint packages are the previous scope of myparcelnl/eslint and sit one minor behind. The @myparcel-dev packages come from the same repo and are the current publish target. Declared @myparcel/prettier-config, which the prettier field already named but nothing installed. Without it eslint aborts on the prettier/prettier rule. Dropped the dead @myparcel-eslint/* glob from the dependabot cooldown list; @myparcel-dev/* was already there. Refs INT-1849 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Applies the autofixable rules in one go, so later PRs do not carry unrelated formatting changes on the files they happen to touch. Refs INT-1849 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replaces @myparcel/prettier-config with @myparcel-dev/prettier-config and declares it. The prettier field already named a config package that nothing installed, so eslint aborted on the prettier/prettier rule. @myparcel/prettier-config 1.1.0 is deprecated on npm; the two configs are byte-identical, so formatting does not change. Refs INT-1849 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Adds extraFileExtensions to the .ts override so the shared TypeScript program knows about .vue. typescript-eslint builds one program per run. The .vue override got extraFileExtensions from @vue/eslint-config-typescript, the .ts override did not, so the program created first excluded .vue. Every one of the 81 .vue files then failed with "Parsing error: ESLint was configured to run on <file> using parserOptions.project" and no rule ever ran on them. Linting only .vue files hid it, because that run built a program that did know the extension. Refs INT-1849 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Extends the earlier fix pass to the 45 .vue files that could not be parsed before. Refs INT-1849 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
FreekVR
force-pushed
the
chore/eslint-config-dev-scope
branch
from
September 3, 2026 15:18
7b26d1a to
6661639
Compare
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.
Moves the eslint config references from @myparcel-eslint to @myparcel-dev.
The @myparcel-eslint packages are the previous scope of myparcelnl/eslint and sit one minor behind. The @myparcel-dev packages come from the same repo and are the current publish target. Pinned to what is published there: ^1.4.0, and ^1.3.0 for eslint-config-import.
Declared the prettier config that the prettier field already named but nothing installed. Without it eslint aborts on the prettier/prettier rule.
The second commit is a one-time eslint --fix pass, so later PRs do not carry unrelated formatting changes on the files they happen to touch. It is mostly consistent-type-imports.
Refs INT-1849
🤖 Generated with Claude Code