Repository navigation
fix(json-pointer): upgrade to @swaggerexpert/json-pointer v3 - #5260
Open
sebdanielsson wants to merge 1 commit into
Open
sebdanielsson wants to merge 1 commit into
sebdanielsson wants to merge 1 commit into
Conversation
sebdanielsson
force-pushed
the
fix/json-pointer-v3
branch
from
October 17, 2026 10:11
3c0c209 to
5786cd1
Compare
sebdanielsson
force-pushed
the
fix/json-pointer-v3
branch
2 times, most recently
from
October 27, 2026 12:40
ff99736 to
e320742
Compare
v3 no longer ships the ApiDOM evaluation realm, whose v2 copy imported @swagger-api/apidom-core without declaring it. The realm now lives in this package, which depends on apidom-core, and the public evaluate signature is unchanged. Invalid JSON Pointers now throw JSONPointerParseError, as in v3.
sebdanielsson
force-pushed
the
fix/json-pointer-v3
branch
from
October 28, 2026 19:54
e320742 to
fa86d1c
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
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.
@swaggerexpert/json-pointerv2's ApiDOM realm imports@swagger-api/apidom-corewithout declaring it, so it only resolves through hoisting and fails under strict node_modules layouts such as pnpm's isolated linker (background: https://nubjs.com/blog/phantom-dependencies-package-extensions). v3 dropped that realm from its npm package, so this moves it intoapidom-json-pointer, which already depends onapidom-core, and upgrades to v3; as in v3, an invalid JSON Pointer now throwsJSONPointerParseErrorinstead ofJSONPointerEvaluateError.