\n\n## Table of Contents\n\n- [Getting started](#getting-started)\n - [Installation](#installation)\n - [Usage](#usage)\n - [Parsing](#parsing)\n - [Translators](#translators)\n - [CST](#cst-translator)\n - [AST](#ast-translator)\n - [XML](#xml-translator)\n - [Statistics](#statistics)\n - [Tracing](#tracing)\n - [Validation](#validation)\n - [Escaping](#escaping)\n - [Evaluation](#evaluation)\n - [Strict Arrays](#strict-arrays)\n - [Strict Objects](#strict-objects)\n - [Evaluation Realms](#evaluation-realms)\n - [JSON](#json-evaluation-realm)\n - [Map/Set](#mapset-evaluation-realm)\n - [Custom](#custom-evaluation-realms)\n - [Composing Realms](#composing-evaluation-realms)\n - [Evaluation Diagnostics](#evaluation-diagnostics)\n - [Evaluation Tracing](#evaluation-tracing)\n - [Compilation](#compilation)\n - [Representation](#representation)\n - [JSON String](#json-string)\n - [URI Fragment Identifier](#uri-fragment-identifier)\n - [Errors](#errors)\n - [Grammar](#grammar)\n- [More about JSON Pointer](#more-about-json-pointer)\n- [License](#license)\n\n\n## Getting started\n\n### Installation\n\nYou can install `@swaggerexpert/json-pointer` using `npm`:\n\n```sh\n $ npm install @swaggerexpert/json-pointer\n```\n\n---\n\n**[unpkg.com](https://unpkg.com/)**\n\nInclude following script tag into your HTML file:\n\n```html\n\n```\n\nGlobal variable `JSONPointer` will be available in the browser matching interface of `@swaggerexpert/json-pointer` npm package.\n`json-pointer.browser.min.js` is [UMD](https://github.com/umdjs/umd?tab=readme-ov-file#umd-universal-module-definition) minified build artifact.\nThere is also unminified `json-pointer.browser.js` artifact, suitable for debugging.\n\n---\n\n**[jsDelivr](https://www.jsdelivr.com/)**\n\nInclude following script tag into your HTML file (ESM mode):\n\n```html\n\n```\nLocal variable `JSONPointer` will be available in scope of the `\n```\n\nGlobal variable `JSONPointer` will be available in the browser matching interface of `@swaggerexpert/json-pointer` npm package.\n`json-pointer.browser.min.js` is [UMD](https://github.com/umdjs/umd?tab=readme-ov-file#umd-universal-module-definition) minified build artifact.\nThere is also unminified `json-pointer.browser.js` artifact, suitable for debugging.\n\n### Usage\n\n`@swaggerexpert/json-pointer` currently supports **parsing**, **validation** ,**evaluation**, **compilation** and **representation**.\nBoth parser and validator are based on a superset of [ABNF](https://www.rfc-editor.org/rfc/rfc5234) ([SABNF](https://cs.github.com/ldthomas/apg-js2/blob/master/SABNF.md))\nand use [apg-lite](https://github.com/ldthomas/apg-lite) parser generator.\n\n#### Parsing\n\nParsing a JSON Pointer is as simple as importing the **parse** function and calling it.\n\n```js\nimport { parse } from '@swaggerexpert/json-parse';\n\nconst parseResult = parse('/foo/bar');\n```\n\n**parseResult** variable has the following shape:\n\n```\n{\n result: ,\n tree: ,\n stats: ,\n trace: ,\n}\n```\n\n[TypeScript typings](https://github.com/swaggerexpert/json-pointer/blob/main/types/index.d.ts) are available for all fields attached to parse result object returned by the `parse` function.\n\n##### Translators\n\n`@swaggerexpert/json-pointer` provides several translators to convert the parse result into different tree representations.\n\n###### CST translator\n\n[Concrete Syntax Tree](https://en.wikipedia.org/wiki/Parse_tree) (Parse tree) representation is available on parse result\nwhen instance of `CSTTranslator` is provided via a `translator` option to the `parse` function.\nCST is suitable to be consumed by other tools like IDEs, editors, etc...\n\n```js\nimport { parse, CSTTranslator } from '@swaggerexpert/json-pointer';\n\nconst { tree: CST } = parse('/foo/bar', { translator: new CSTTranslator() });\n```\n\nCST tree has a shape documented by [TypeScript typings (CSTTree)](https://github.com/swaggerexpert/json-pointer/blob/main/types/index.d.ts).\n\n###### AST translator\n\n**Default translator**. [Abstract Syntax Tree](https://en.wikipedia.org/wiki/Abstract_syntax_tree) representation is available on parse result\nby default or when instance of `ASTTranslator` is provided via a `translator` option to the `parse` function.\nAST is suitable to be consumed by implementations that need to analyze the structure of the JSON Pointer\nor for building a custom JSON Pointer evaluation engine.\n\nAST of the parsed JSON Pointer is a list of unescaped reference tokens.\n\n```js\nimport { parse } from '@swaggerexpert/json-pointer';\n\nconst { tree: AST } = parse('/foo/bar'); // AST = ['foo', 'bar']\n```\n\nor\n\n```js\nimport { parse, ASTTranslator } from '@swaggerexpert/json-poiner';\n\nconst { tree: AST } = parse('/foo/bar', { translator: new ASTTranslator() }); // AST = ['foo', 'bar']\n```\n\n###### XML translator\n\n```js\nimport { parse, XMLTranslator } from '@swaggerexpert/json-pointer';\n\nconst { tree: XML } = parse('$.store.book[0].title', { translator: new XMLTranslator() });\n```\n\n##### Statistics\n\n`parse` function returns additional statistical information about the parsing process.\nCollection of the statistics can be enabled by setting `stats` option to `true`.\n\n```js\nimport { parse } from '@swaggerexpert/json-pointer';\n\nconst { stats } = parse('/foo/bar', { stats: true });\n\nstats.displayStats(); // returns operator stats\nstats.displayHits(); // returns rules grouped by hit count\n```\n\n##### Tracing\n\n`parse` function returns additional tracing information about the parsing process.\nTracing can be enabled by setting `trace` option to `true`. Tracing is essential\nfor debugging failed matches or analyzing rule execution flow.\n\n```js\nimport { parse } from '@swaggerexpert/json-pointer';\n\nconst { result, trace } = parse('1', { trace: true });\n\nresult.success; // returns false\ntrace.displayTrace(); // returns trace information\ntrace.inferExpectations(); // returns parser expectations\n```\n\nBy combining information from `result` and `trace`, it is possible to analyze the parsing process in detail\nand generate a messages like this: `'Invalid JSON Pointer: \"1\". Syntax error at position 0, expected \"/\"'`. Please see this\n[test file](https://github.com/swaggerexpert/json-pointer/blob/main/test/parse/trace.js) for more information how to achieve that.\n\n#### Validation\n\nValidating a JSON Pointer is as simple as importing one of the validation functions and calling it.\n\n```js\nimport {\n testJSONPointer,\n testReferenceToken,\n testArrayLocation,\n testArrayIndex,\n testArrayDash\n} from '@swaggerexpert/json-pointer';\n\ntestJSONPointer('/foo/bar'); // => true\ntestReferenceToken('foo'); // => true\ntestArrayLocation('0'); // => true\ntestArrayLocation('-'); // => true\ntestArrayIndex('0'); // => true\ntestArrayDash('-'); // => true\n```\n\n#### Escaping\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\nBecause the characters `'~'` (%x7E) and `'/'` (%x2F) have special\nmeanings in JSON Pointer, `'~'` needs to be encoded as `'~0'` and `'/'`\nneeds to be encoded as `'~1'` when these characters appear in a\nreference token.\n\n```js\nimport { escape } from '@swaggerexpert/json-pointer';\n\nescape('~foo'); // => '~0foo'\nescape('/foo'); // => '~1foo'\n```\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\nUnescape is performed by first transforming any\noccurrence of the sequence `'~1'` to `'/'`, and then transforming any\noccurrence of the sequence `'~0'` to `'~'`. By performing the\nsubstitutions in this order, this library avoids the error of\nturning `'~01'` first into `'~1'` and then into `'/'`, which would be\nincorrect (the string `'~01'` correctly becomes `'~1'` after transformation).\n\n```js\nimport { unescape } from '@swaggerexpert/json-pointer';\n\nunescape('~0foo'); // => '~foo'\nunescape('~1foo'); // => '/foo'\n```\n\n#### Evaluation\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\nEvaluation of a JSON Pointer begins with a reference to the root\nvalue of a JSON document and completes with a reference to some value\nwithin the document. Each reference token in the JSON Pointer is\nevaluated sequentially.\n\n```js\nimport { evaluate } from '@swaggerexpert/json-pointer';\n\nconst value = {\n \"foo\": [\"bar\", \"baz\"],\n \"\": 0,\n \"a/b\": 1,\n \"c%d\": 2,\n \"e^f\": 3,\n \"g|h\": 4,\n \"i\\\\j\": 5,\n \"k\\\"l\": 6,\n \" \": 7,\n \"m~n\": 8\n};\n\nevaluate(value, ''); // => identical to value\nevaluate(value, '/foo'); // => [\"bar\", \"baz\"]\nevaluate(value, '/foo/0'); // => \"bar\"\nevaluate(value, '/'); // => 0\nevaluate(value, '/a~1b'); // => 1\nevaluate(value, '/c%d'); // => 2\nevaluate(value, '/e^f'); // => 3\nevaluate(value, '/g|h'); // => 4\nevaluate(value, '/i\\\\j'); // => 5\nevaluate(value, '/k\"l'); // => 6\nevaluate(value, '/ '); // => 7\nevaluate(value, '/m~0n'); // => 8\n\n// neither object nor array\nevaluate(null, '/foo'); // => throws JSONPointerTypeError\n// arrays\nevaluate(value, '/foo/2'); // => throws JSONPointerIndexError\nevaluate(value, '/foo/-'); // => throws JSONPointerIndexError\nevaluate(value, '/foo/a'); // => throws JSONPointerIndexError\n// objects\nevaluate(value, '/bar'); // => throws JSONPointerKeyError\n```\n\n###### Strict Arrays\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\nBy default, the evaluation is **strict**, meaning an error condition will be raised if it fails to\nresolve a concrete value for any of the JSON pointer's reference tokens. For example, if an array\nis referenced with a non-numeric token, an error condition will be raised.\n\nNote that the use of the `\"-\"` character to index an array will always\nresult in such an error condition because by definition it refers to\na nonexistent array element.\n\nThis spec compliant strict behavior can be disabled by setting the `strictArrays` option to `false`.\n\n```js\nevaluate(value, '/foo/2', { strictArrays: false }); // => undefined\nevaluate(value, '/foo/-', { strictArrays: false }); // => undefined\nevaluate(value, '/foo/132423', { strictArrays: false }); // => undefined\n```\n\n###### Strict Objects\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\nBy default, the evaluation is **strict**, meaning error condition will be raised if it fails to\nresolve a concrete value for any of the JSON pointer's reference tokens. For example,\nif a token references a key that is not present in an object, an error condition will be raised.\n\nThis spec compliant strict behavior can be disabled by setting the `strictObjects` option to `false`.\n\n```js\nevaluate(value, '/bar', { strictObjects: false }); // => undefined\n```\n\n`strictObjects` options has no effect in cases where evaluation of previous\nreference token failed to resolve a concrete value.\n\n```js\nevaluate(value, '/bar/baz', { strictObjects: false }); // => throw JSONPointerTypeError\n```\n\n##### Evaluation Realms\n\nAn **evaluation realm** defines the rules for interpreting and navigating data structures in JSON Pointer evaluation.\nWhile JSON Pointer traditionally operates on JSON objects and arrays, evaluation realms allow the evaluation to work\npolymorphically with different data structures, such as [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map),\n[Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set), [Immutable.js](https://immutable-js.com/),\nor even custom representations like [SpecLynx ApiDOM](https://github.com/speclynx/apidom).\nRealm can be specified via the `realm` option in the `evalute()` function.\n\n###### JSON Evaluation Realm\n\nBy default, the evaluation operates under the **JSON realm**, which assumes that:\n\n- **Arrays** are indexed numerically.\n- **Objects** (plain JavaScript objects) are accessed by string keys.\n\nThe default realm is represented by the `JSONEvaluationRealm` class.\n\n```js\nimport { evaluate } from '@swaggerexpert/json-pointer';\n\nevaluate({ a: 'b' }, '/a'); // => 'b'\n```\n\nis equivalent to:\n\n```js\nimport { evaluate } from '@swaggerexpert/json-pointer';\nimport JSONEvaluationRealm from '@swaggerexpert/json-pointer/evaluate/realms/json';\n\nevaluate({ a: 'b' }, '/a', { realm: new JSONEvaluationRealm() }); // => 'b'\n```\n\n###### Map/Set Evaluation Realm\n\nThe Map/Set realm extends JSON Pointer evaluation to support [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) and [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) instances,\nallowing structured traversal and access beyond traditional JavaScript objects and arrays.\nMap/Set realm is represented by the `MapSetEvaluationRealm` class.\n\n\n```js\nimport { evaluate } from '@swaggerexpert/json-pointer';\nimport MapSetEvaluationRealm from '@swaggerexpert/json-pointer/evaluate/realms/map-set';\n\nconst map = new Map([\n ['a', new Set(['b', 'c'])]\n]);\n\nevaluate(map, '/a/1', { realm: new MapSetEvaluationRealm() }); // => 'c'\n```\n\n###### Custom Evaluation Realms\n\nThe evaluation is designed to support **custom evaluation realms**,\nenabling JSON Pointer evaluation for **non-standard data structures**.\n\nA valid custom evaluation realm must match the structure of the [EvaluationRealm interface](https://github.com/swaggerexpert/json-pointer/blob/main/types/index.d.ts).\n\nOne way to create a custom realm is to extend the `EvaluationRealm` class and implement the required methods.\n\n```js\nimport { evaluate, EvaluationRealm } from '@swaggerexpert/json-pointer';\n\nclass CustomEvaluationRealm extends EvaluationRealm {\n name = 'cusotm';\n\n isArray(node) { ... }\n isObject(node) { ... }\n sizeOf(node) { ... }\n has(node, referenceToken) { ... }\n evaluate(node, referenceToken) { ... }\n}\n\nevaluate({ a: 'b' }, '/a', { realm: new CustomEvaluationRealm() }); // => 'b'\n```\n\nReference implementations for [Minim](https://github.com/refractproject/minim), [SpecLynx ApiDOM](https://github.com/speclynx/apidom),\nand [Immutable.js](https://immutable-js.com/) are available in the [`contrib/realms/`](https://github.com/swaggerexpert/json-pointer/tree/main/contrib/realms) directory.\nThese can be copied and adapted for your specific needs.\n\n###### Composing Evaluation Realms\n\nEvaluation realms can be composed to create complex evaluation scenarios,\nallowing JSON Pointer evaluation to work across multiple data structures in a seamless manner.\nBy combining different realms, composite evaluation ensures that a JSON Pointer query can\nresolve correctly whether the data structure is an object, array, Map, Set, or any custom type.\n\nWhen composing multiple evaluation realms, the **order matters**. The composition is performed from left to right, meaning:\n\n- More specific realms should be placed first (leftmost position).\n- More generic realms should be placed later (rightmost position).\n\nThis ensures that specialized data structures (e.g., Map, Set, Immutable.js) take precedence over generic JavaScript objects and arrays.\n\n```js\nimport { composeRealms, evaluate } from '@swaggerexpert/json-pointer';\nimport JSONEvaluationRealm from '@swaggerexpert/json-pointer/realms/json';\nimport MapSetEvaluationRealm from '@swaggerexpert/json-pointer/realms/map-set';\n\nconst compositeRealm = composeRealms(new MapSetEvaluationRealm(), new JSONEvaluationRealm());\n\nconst structure = [\n {\n a: new Map([\n ['b', new Set(['c', 'd'])]\n ]),\n },\n];\n\nevaluate(structure, '/0/a/b/1', { realm : compositeRealm }); // => 'd'\n```\n\n##### Evaluation Diagnostics\n\n`@swaggerexpert/json-pointer` provides rich diagnostic information to help identify and resolve issues during JSON Pointer evaluation.\n\nWhen evaluation fails, the library throws [errors](#errors) from a well-defined hierarchy — all extending from `JSONPointerEvaluateError`.\nThese errors carry detailed diagnostic metadata describing what failed, where it failed, and why.\n\nEach error includes following fields:\n\n- `jsonPointer` – the full pointer being evaluated\n- `referenceToken` – the token that caused the failure\n- `referenceTokenPosition` – the index of that token within the pointer\n- `referenceTokens` – the full list of parsed reference tokens\n- `currentValue` – the value being evaluated at the point of failure\n- `realm` – the name of the evaluation realm (e.g., \"json\")\n\n##### Evaluation Tracing\n\n`@swaggerexpert/json-pointer` package supports evaluation tracing, allowing you to inspect each step of JSON Pointer evaluation in detail.\nThis is especially useful for debugging, error reporting, visualization tools, or implementing custom behavior like fallbacks and partial evaluations.\n\nHow it works?\n\nTo enable tracing, provide an empty trace object when calling evaluate.\n`trace` object is populated with detailed information about each step of the evaluation process:\n\nTracing `successful` evaluation:\n\n```js\nimport { evaluate } from '@swaggerexpert/json-pointer';\n\nconst trace = {};\nevaluate({ a: 'b' }, '/a', { trace });\n```\n\n```js\n// trace\n{\n steps: [\n {\n referenceToken: 'a',\n referenceTokenPosition: 0,\n input: { a: 'b' },\n inputType: 'object',\n output: 'b',\n success: true\n }\n ],\n failed: false,\n failedAt: -1,\n message: 'JSON Pointer \"/a\" successfully evaluated against the provided value',\n context: {\n jsonPointer: '/a',\n referenceTokens: [ 'a' ],\n strictArrays: true,\n strictObjects: true,\n realm: 'json',\n value: { a: 'b' }\n }\n}\n```\n\nTracing `failed` evaluation:\n\n```js\nimport { evaluate } from '@swaggerexpert/json-pointer';\n\nconst trace = {};\ntry {\n evaluate({ a: 'b' }, '/c', { trace });\n} catch {}\n```\n\n```js\n// trace\n{\n steps: [\n {\n referenceToken: 'c',\n referenceTokenPosition: 0,\n input: { a: 'b' },\n inputType: 'object',\n output: undefined,\n success: false,\n reason: 'Invalid object key \"c\" at position 0 in \"/c\": key not found in object'\n }\n ],\n failed: true,\n failedAt: 0,\n message: 'Invalid object key \"c\" at position 0 in \"/c\": key not found in object',\n context: {\n jsonPointer: '/c',\n referenceTokens: [ 'c' ],\n strictArrays: true,\n strictObjects: true,\n realm: 'json',\n value: { a: 'b' }\n }\n}\n```\n\n`trace` option can additionally be set to `true` to enable parse tracing without providing an empty object.\nWhen parsing of the JSON Pointer fails during evaluation, the generated error will contain additional information explaining the failure.\nThis is the default behavior of the `trace` option. You can also set `trace` to `false` to disable tracing entirely.\n\n#### Compilation\n\nCompilation is the process of transforming a list of unescaped reference tokens into a JSON Pointer.\nReference tokens are escaped before compiled into a JSON Pointer.\n\n```js\nimport { compile } from '@swaggerexpert/json-pointer';\n\ncompile(['~foo', 'bar']); // => '/~0foo/bar'\n```\n\n#### Representation\n\n##### JSON String\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\nA JSON Pointer can be represented in a JSON string value. Per\n[RFC4627, Section 2.5](https://datatracker.ietf.org/doc/html/rfc4627#section-2.5), all instances of quotation mark `'\"'` (%x22),\nreverse solidus `'\\'` (%x5C), and control (%x00-1F) characters MUST be\nescaped.\n\n```js\nimport { JSONString } from '@swaggerexpert/json-pointer';\n\nJSONString.to('/foo\"bar'); // => '\"/foo\\\\\"bar\"'\nJSONString.from('\"/foo\\\\\"bar\"'); // => '/foo\"bar'\n```\n\n##### URI Fragment Identifier\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\nA JSON Pointer can be represented in a URI fragment identifier by\nencoding it into octets using UTF-8 [RFC3629](https://datatracker.ietf.org/doc/html/rfc3629), while percent-encoding\nthose characters not allowed by the fragment rule in [RFC3986](https://datatracker.ietf.org/doc/html/rfc3986#section-3.5).\n\n```js\nimport { URIFragmentIdentifier } from '@swaggerexpert/json-pointer';\n\nURIFragmentIdentifier.to('/foo\"bar'); // => '#/foo%22bar'\nURIFragmentIdentifier.from('#/foo%22bar'); // => '/foo\"bar'\nURIFragmentIdentifier.fromURIReference('https://swaggerexpert.com/path#/foo%22bar'); // => '/foo\"bar'\n```\n\n#### Errors\n\n`@swaggerexpert/json-pointer` provides a structured error class hierarchy,\nenabling precise error handling across JSON Pointer operations, including parsing, evaluation, compilation and validation.\n\n```js\nimport {\n JSONPointerError,\n JSONPointerParseError,\n JSONPointerCompileError,\n JSONPointerEvaluateError,\n JSONPointerTypeError,\n JSONPointerKeyError,\n JSONPointerIndexError\n} from '@swaggerexpert/json-pointer';\n```\n\n**JSONPointerError** is the base class for all JSON Pointer errors.\n\n#### Grammar\n\nNew grammar instance can be created in following way:\n\n```js\nimport { Grammar } from '@swaggerexpert/json-pointer';\n\nconst grammar = new Grammar();\n```\n\nTo obtain original ABNF (SABNF) grammar as a string:\n\n```js\nimport { Grammar } from '@swaggerexpert/json-pointer';\n\nconst grammar = new Grammar();\n\ngrammar.toString();\n// or\nString(grammar);\n```\n\n## More about JSON Pointer\n\nJSON Pointer is defined by the following [ABNF](https://tools.ietf.org/html/rfc5234) syntax\n\n[comment]: <> (SPDX-FileCopyrightText: Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.)\n[comment]: <> (SPDX-License-Identifier: BSD-2-Clause)\n\n```abnf\n; JavaScript Object Notation (JSON) Pointer ABNF syntax\n; https://datatracker.ietf.org/doc/html/rfc6901\njson-pointer = *( slash reference-token ) ; MODIFICATION: surrogate text rule used\nreference-token = *( unescaped / escaped )\nunescaped = %x00-2E / %x30-7D / %x7F-10FFFF\n ; %x2F ('/') and %x7E ('~') are excluded from 'unescaped'\nescaped = \"~\" ( \"0\" / \"1\" )\n ; representing '~' and '/', respectively\n\n; https://datatracker.ietf.org/doc/html/rfc6901#section-4\narray-location = array-index / array-dash\narray-index = %x30 / ( %x31-39 *(%x30-39) )\n ; \"0\", or digits without a leading \"0\"\narray-dash = \"-\"\n\n; Surrogate named rules\nslash = \"/\"\n```\n\n## License\n\n`@swaggerexpert/json-pointer` is licensed under [Apache 2.0 license](https://github.com/swaggerexpert/json-pointer/blob/main/LICENSE).\n`@swaggerexpert/json-pointer` comes with an explicit [NOTICE](https://github.com/swaggerexpert/json-pointer/blob/main/NOTICE) file\ncontaining additional legal notices and information.","users":{}}
![\"Tidelift\"](\"https://cdn2.hubspot.net/hubfs/4008838/website/logos/logos_for_download/Tidelift_primary-shorthand-logo.png\"){kind=logo}
\n