Repository navigation
fix(deps): sync lockfile with the ajv@8 peer of @hookform/resolvers - #32
Merged
Merged
Conversation
npm ci failed with EUSAGE: package.json and package-lock.json were out of
sync ("lock file's ajv@6.15.0 does not satisfy ajv@8.20.0").
@hookform/resolvers is declared as ^5.2.2 and resolves to 5.9.1, which
declares an optional peer dependency on ajv@^8.12.0. optional means npm
will not error when the peer cannot be installed; it does not mean npm
skips it. So the correct tree hoists ajv@8.20.0 to the root and nests
eslint's ajv@6.15.0 under eslint/ and @eslint/eslintrc/.
The committed lockfile carried only ajv@6.15.0 at the root and no ajv@8
at all. It was last regenerated in 77d24fe, when the monorepo was
collapsed, and never accounted for that peer.
Regenerated with npm install. package.json is unchanged. The diff is 12
additions and no removals; the two apparent version changes are hoisting
moves, so eslint still resolves the same ajv@6.15.0 it did before.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch had an error being 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.
npm ci failed with EUSAGE: package.json and package-lock.json were out of sync ("lock file's ajv@6.15.0 does not satisfy ajv@8.20.0").
@hookform/resolvers is declared as ^5.2.2 and resolves to 5.9.1, which declares an optional peer dependency on ajv@^8.12.0. optional means npm will not error when the peer cannot be installed; it does not mean npm skips it. So the correct tree hoists ajv@8.20.0 to the root and nests eslint's ajv@6.15.0 under eslint/ and @eslint/eslintrc/.
The committed lockfile carried only ajv@6.15.0 at the root and no ajv@8 at all. It was last regenerated in 77d24fe, when the monorepo was collapsed, and never accounted for that peer.
Regenerated with npm install. package.json is unchanged. The diff is 12 additions and no removals; the two apparent version changes are hoisting moves, so eslint still resolves the same ajv@6.15.0 it did before.