You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
package.json pins "eslint-plugin-prettier": "^4.2.1" (locked to 4.2.5). Current published major on npm is 5.5.6 — one major ahead. eslint-plugin-prettier@5.5.6's peer requirements (verified via npm view eslint-plugin-prettier@5.5.6 peerDependencies) are prettier: ">=3.0.0" and eslint-config-prettier: ">=7.0.0 <10.0.0 || >=10.1.0". This repo currently has prettier@^2.8.3 and eslint-config-prettier@^8.6.0, neither of which satisfies those ranges yet — bumping prettier is already tracked in #38 (→ ^3.9.6) and bumping eslint-config-prettier is already tracked in #47 (→ ^10.1.8), and both of those issues explicitly scope out touching eslint-plugin-prettier. This issue is the resulting follow-up once both prerequisites land.
eslint-plugin-prettier devDependency in package.json is bumped to ^5.5.6, with package-lock.json updated accordingly.
npm run lint passes with zero errors (the prettier/prettier rule wired in via .eslintrc.cjs's plugin:prettier/recommended continues to resolve and run correctly against the new plugin major).
npm run format:check still passes.
Scope
Only the eslint-plugin-prettier version bump, gated on its prerequisites (#38, #47) already being merged. Do not re-bump prettier or eslint-config-prettier here (tracked separately), and do not change .eslintrc.cjs rules beyond whatever is strictly needed to keep plugin:prettier/recommended resolving.
Problem
package.jsonpins"eslint-plugin-prettier": "^4.2.1"(locked to4.2.5). Current published major on npm is5.5.6— one major ahead.eslint-plugin-prettier@5.5.6's peer requirements (verified vianpm view eslint-plugin-prettier@5.5.6 peerDependencies) areprettier: ">=3.0.0"andeslint-config-prettier: ">=7.0.0 <10.0.0 || >=10.1.0". This repo currently hasprettier@^2.8.3andeslint-config-prettier@^8.6.0, neither of which satisfies those ranges yet — bumping prettier is already tracked in #38 (→^3.9.6) and bumping eslint-config-prettier is already tracked in #47 (→^10.1.8), and both of those issues explicitly scope out touchingeslint-plugin-prettier. This issue is the resulting follow-up once both prerequisites land.Acceptance criteria
prettieris at^3.xandeslint-config-prettieris at^10.1.xor later). If either is still open, leave this issue open and do not attempt the bump yet.eslint-plugin-prettierdevDependency inpackage.jsonis bumped to^5.5.6, withpackage-lock.jsonupdated accordingly.npm run lintpasses with zero errors (theprettier/prettierrule wired in via.eslintrc.cjs'splugin:prettier/recommendedcontinues to resolve and run correctly against the new plugin major).npm run format:checkstill passes.Scope
Only the
eslint-plugin-prettierversion bump, gated on its prerequisites (#38, #47) already being merged. Do not re-bumpprettieroreslint-config-prettierhere (tracked separately), and do not change.eslintrc.cjsrules beyond whatever is strictly needed to keepplugin:prettier/recommendedresolving.