Repository navigation
fix(nextjs-x402): regenerate package-lock to match package.json - #101
Merged
Merged
Conversation
#84 switched nirium from file:../../packages/sdk to ^0.10.1 in package.json but kept the old lock, where nirium is still a link to the local SDK. npm ci has failed in this example since then. Regenerated against the current package.json (nirium resolves to 0.10.2) and bumped fast-uri to 3.1.8 in the same pass. npm ci, npm test (7/7), typecheck and next build all pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 cihas failed inexamples/nextjs-x402since #84. That PR changedniriuminpackage.jsonfromfile:../../packages/sdkto^0.10.1, but the lock still hasniriumas a link to the local SDK.Regenerated the lock against the current
package.json(niriumresolves to 0.10.2) and bumpedfast-urito 3.1.8 in the same pass. Most of the diff is the registryniriumdependency tree replacing the old link.Checked:
npm ci,npm test(7/7),npm run typecheck,npm run build.Overlaps with #99, which bumps
fast-uriin this same lockfile. Whichever merges second will conflict on this file; the right resolution is to take this PR's version.Not in this PR:
^0.10.1stays below the currentnirium(0.16.0). Bumping the example to^0.16.0would be a separate change.🤖 Generated with Claude Code