chore(release): release v11.0.3

Chevrotain · Aug 14, 2023 · ac58066 · ac58066
1 parent d50420d
commit ac58066
Show file tree

Hide file tree

Showing 38 changed files with 156 additions and 124 deletions.
diff --git a/README.md b/README.md
@@ -36,8 +36,8 @@ A more in depth review of Chevrotain can be found in this great article on: [Par
     - `https://unpkg.com/chevrotain/lib/chevrotain.mjs`
     - `https://unpkg.com/chevrotain/lib/chevrotain.min.mjs`
   - Explicit version number:
-    - `https://unpkg.com/[email protected].2/lib/chevrotain.mjs`
-    - `https://unpkg.com/[email protected].2/lib/chevrotain.min.mjs`
+    - `https://unpkg.com/[email protected].3/lib/chevrotain.mjs`
+    - `https://unpkg.com/[email protected].3/lib/chevrotain.min.mjs`
 
 ## Documentation & Resources
 

diff --git a/examples/grammars/package.json b/examples/grammars/package.json
@@ -1,6 +1,6 @@
 {
   "name": "chevrotain_examples_grammars",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "type": "module",
   "scripts": {
     "ci": "pnpm run test && pnpm run bundle:graphql",
@@ -9,7 +9,7 @@
   },
   "dependencies": {
     "acorn": "8.8.0",
-    "chevrotain": "11.0.2",
+    "chevrotain": "11.0.3",
     "xregexp": "5.1.1"
   },
   "devDependencies": {

diff --git a/examples/implementation_languages/package.json b/examples/implementation_languages/package.json
@@ -1,6 +1,6 @@
 {
   "name": "chevrotain_examples_implementation_languages",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "type": "module",
   "scripts": {
     "ci": "pnpm run build test",
@@ -9,7 +9,7 @@
     "test": "mocha \"*spec.js\""
   },
   "dependencies": {
-    "chevrotain": "11.0.2"
+    "chevrotain": "11.0.3"
   },
   "devDependencies": {
     "coffee-script": "^1.11.1",

diff --git a/examples/lexer/package.json b/examples/lexer/package.json
@@ -1,13 +1,13 @@
 {
   "name": "chevrotain_examples_lexer",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "type": "module",
   "scripts": {
     "ci": "pnpm run test",
     "test": "mocha \"!(node_modules)/**/*spec.js\""
   },
   "dependencies": {
-    "chevrotain": "11.0.2",
+    "chevrotain": "11.0.3",
     "lodash": "4.17.21"
   },
   "private": true

diff --git a/examples/parser/package.json b/examples/parser/package.json
@@ -1,14 +1,14 @@
 {
   "name": "chevrotain_examples_parser",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "type": "module",
   "scripts": {
     "ci": "pnpm run test",
     "test": "mocha \"!(node_modules)/**/*spec.js\"",
     "bundle:diagrams": "esbuild ./diagrams/grammar.js --bundle --minify --format=esm --outfile=./diagrams/gen/grammar-bundled.min.mjs"
   },
   "dependencies": {
-    "chevrotain": "11.0.2",
+    "chevrotain": "11.0.3",
     "lodash": "4.17.21"
   },
   "devDependencies": {

diff --git a/examples/tutorial/package.json b/examples/tutorial/package.json
@@ -1,13 +1,13 @@
 {
   "name": "chevrotain_examples_tutorial",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "type": "module",
   "scripts": {
     "ci": "pnpm run test",
     "test": "mocha \"step*/*spec.js\""
   },
   "dependencies": {
-    "chevrotain": "11.0.2",
+    "chevrotain": "11.0.3",
     "lodash": "4.17.21"
   },
   "private": true

diff --git a/lerna.json b/lerna.json
@@ -6,5 +6,5 @@
       "exact": true
     }
   },
-  "version": "11.0.2"
+  "version": "11.0.3"
 }
diff --git a/packages/chevrotain/package.json b/packages/chevrotain/package.json
@@ -1,6 +1,6 @@
 {
   "name": "chevrotain",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "description": "Chevrotain is a high performance fault tolerant javascript parsing DSL for building recursive decent parsers",
   "keywords": [
     "parser",
@@ -67,11 +67,11 @@
     "bundle:esm:min": "esbuild ./lib/src/api.js --bundle --minify --format=esm --sourcemap --outfile=lib/chevrotain.min.mjs"
   },
   "dependencies": {
-    "@chevrotain/cst-dts-gen": "11.0.2",
-    "@chevrotain/gast": "11.0.2",
-    "@chevrotain/regexp-to-ast": "11.0.2",
-    "@chevrotain/types": "11.0.2",
-    "@chevrotain/utils": "11.0.2",
+    "@chevrotain/cst-dts-gen": "11.0.3",
+    "@chevrotain/gast": "11.0.3",
+    "@chevrotain/regexp-to-ast": "11.0.3",
+    "@chevrotain/types": "11.0.3",
+    "@chevrotain/utils": "11.0.3",
     "lodash-es": "4.17.21"
   },
   "devDependencies": {

diff --git a/packages/chevrotain/src/version.ts b/packages/chevrotain/src/version.ts
@@ -1,4 +1,4 @@
 // needs a separate module as this is required inside chevrotain productive code
 // and also in the entry point for webpack(api.ts).
 // A separate file avoids cyclic dependencies and webpack errors.
-export const VERSION = "11.0.2";
+export const VERSION = "11.0.3";
diff --git a/packages/cst-dts-gen-test/package.json b/packages/cst-dts-gen-test/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@chevrotain/cst-dts-gen-test",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "private": true,
   "description": "tests for @chevrotain/cst-dts-gen",
   "license": "Apache-2.0",
@@ -23,10 +23,10 @@
     "coverage": "c8 mocha --enable-source-maps"
   },
   "dependencies": {
-    "@chevrotain/cst-dts-gen": "11.0.2",
-    "@chevrotain/gast": "11.0.2",
-    "@chevrotain/types": "11.0.2",
-    "chevrotain": "11.0.2",
+    "@chevrotain/cst-dts-gen": "11.0.3",
+    "@chevrotain/gast": "11.0.3",
+    "@chevrotain/types": "11.0.3",
+    "chevrotain": "11.0.3",
     "lodash-es": "4.17.21"
   },
   "devDependencies": {

diff --git a/packages/cst-dts-gen/package.json b/packages/cst-dts-gen/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@chevrotain/cst-dts-gen",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "description": "Generates type definitions for Chevrotain CST nodes",
   "keywords": [],
   "bugs": {
@@ -36,8 +36,8 @@
     "compile": "tsc"
   },
   "dependencies": {
-    "@chevrotain/gast": "11.0.2",
-    "@chevrotain/types": "11.0.2",
+    "@chevrotain/gast": "11.0.3",
+    "@chevrotain/types": "11.0.3",
     "lodash-es": "4.17.21"
   },
   "devDependencies": {

diff --git a/packages/gast/package.json b/packages/gast/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@chevrotain/gast",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "description": "Grammar AST structure for Chevrotain Parsers",
   "keywords": [],
   "bugs": {
@@ -39,7 +39,7 @@
     "coverage": "c8 mocha --enable-source-maps"
   },
   "dependencies": {
-    "@chevrotain/types": "11.0.2",
+    "@chevrotain/types": "11.0.3",
     "lodash-es": "4.17.21"
   },
   "devDependencies": {

diff --git a/packages/regexp-to-ast/package.json b/packages/regexp-to-ast/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@chevrotain/regexp-to-ast",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "description": "Parses a Regular Expression and outputs an AST",
   "keywords": [
     "regExp",

diff --git a/packages/types/package.json b/packages/types/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@chevrotain/types",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "description": "Type Signatures and API Website for Chevrotain",
   "keywords": [],
   "bugs": {

diff --git a/packages/utils/package.json b/packages/utils/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@chevrotain/utils",
-  "version": "11.0.2",
+  "version": "11.0.3",
   "description": "common utilities",
   "keywords": [],
   "bugs": {

diff --git a/packages/website/docs/FAQ.md b/packages/website/docs/FAQ.md
@@ -111,7 +111,7 @@ Special handling is no longer needed during WebPacking scenarios.
 
 The first time a Chevrotain parser is initialized additional validations and computations are performed.
 Some of these can take a very long time under certain edge cases. Specifically the detection of ambiguous alternatives
-when the parser uses a larger than the default [maxLookahead](https://chevrotain.io/documentation/11_0_2/interfaces/IParserConfig.html)
+when the parser uses a larger than the default [maxLookahead](https://chevrotain.io/documentation/11_0_3/interfaces/IParserConfig.html)
 and there are many (thousands) of ambiguous paths.
 
 To resolve this try reducing the maxLookahead and inspect the ambiguity errors to fix

diff --git a/packages/website/docs/changes/CHANGELOG.md b/packages/website/docs/changes/CHANGELOG.md
@@ -1,4 +1,4 @@
-## X.Y.Z (INSERT_DATE_HERE)
+## 11.0.3 (8-15-2023)
 
 #### Bug Fixes
 

diff --git a/packages/website/docs/features/custom_errors.md b/packages/website/docs/features/custom_errors.md
@@ -3,8 +3,8 @@
 Chevrotain allows users to customize both the parser and lexer error messages.
 This can be accomplished by implementing the following interfaces:
 
-- [IParserErrorMessageProvider](https://chevrotain.io/documentation/11_0_2/interfaces/IParserErrorMessageProvider.html)
-- [ILexerErrorMessageProvider](https://chevrotain.io/documentation/11_0_2/interfaces/ILexerErrorMessageProvider.html)
+- [IParserErrorMessageProvider](https://chevrotain.io/documentation/11_0_3/interfaces/IParserErrorMessageProvider.html)
+- [ILexerErrorMessageProvider](https://chevrotain.io/documentation/11_0_3/interfaces/ILexerErrorMessageProvider.html)
 
 See executable examples:
 
@@ -25,7 +25,7 @@ $.RULE("myStatement", () => {
 
 The **ERR_MSG** config property is available for the following DSL methods:
 
-- [CONSUME](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html#CONSUME)
-- [OR](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html#OR)
-- [AT_LEAST_ONE](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html#AT_LEAST_ONE)
-- [AT_LEAST_ONE_SEP](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html#AT_LEAST_ONE_SEP)
+- [CONSUME](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html#CONSUME)
+- [OR](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html#OR)
+- [AT_LEAST_ONE](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html#AT_LEAST_ONE)
+- [AT_LEAST_ONE_SEP](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html#AT_LEAST_ONE_SEP)
diff --git a/packages/website/docs/features/gates.md b/packages/website/docs/features/gates.md
@@ -20,7 +20,7 @@ $.RULE("Value", (isConst) => {
 });
 ```
 
-Using the [Look Ahead](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html#LA) method is often helpful with the use of Gates to determine if a path should be followed or not, for example:
+Using the [Look Ahead](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html#LA) method is often helpful with the use of Gates to determine if a path should be followed or not, for example:
 
 ```javascript
 // SELECT LIMIT.ID FROM USER_LIMIT LIMIT

diff --git a/packages/website/docs/features/grammar_inheritance.md b/packages/website/docs/features/grammar_inheritance.md
@@ -4,8 +4,8 @@ Chevrotain supports Grammar Inheritance, This is useful to represent multiple va
 for example a grammar for ECMAScript 6 **extends** an ECMAScript 5.1 grammar.
 
 Chevrotain Grammars are JavaScript classes, so Grammar inheritance is simply JavaScript inheritance
-with the replacement of the [**RULE**](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html#RULE)
-DSL method with [**OVERRIDE_RULE**](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html#OVERRIDE_RULE) method when needed.
+with the replacement of the [**RULE**](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html#RULE)
+DSL method with [**OVERRIDE_RULE**](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html#OVERRIDE_RULE) method when needed.
 
 See [executable example](https://github.com/chevrotain/chevrotain/tree/master/examples/parser/inheritance)
 for further details.
diff --git a/packages/website/docs/features/position_tracking.md b/packages/website/docs/features/position_tracking.md
@@ -10,7 +10,7 @@ token_skipping
 - start and end lines.
 - start and end columns.
 
-The level of position information tracking can be reduced by using the [**positionTracking**](https://chevrotain.io/documentation/11_0_2/interfaces/ILexerConfig.html#positionTracking) lexer config option.
+The level of position information tracking can be reduced by using the [**positionTracking**](https://chevrotain.io/documentation/11_0_3/interfaces/ILexerConfig.html#positionTracking) lexer config option.
 For example:
 
 ```javascript

diff --git a/packages/website/docs/features/token_grouping.md b/packages/website/docs/features/token_grouping.md
@@ -3,7 +3,7 @@
 Chevrotain lexers support grouping Tokens Types **separately** from the main token vector in the lexing result.
 This is often useful to **collect** a specific set of Token Types for later processing, for example to collect comments tokens.
 
-To group a Token Type simply specify the [**group**](https://chevrotain.io/documentation/11_0_2/interfaces/ITokenConfig.html#group) property in its configuration.
+To group a Token Type simply specify the [**group**](https://chevrotain.io/documentation/11_0_3/interfaces/ITokenConfig.html#group) property in its configuration.
 For example:
 
 ```javascript

diff --git a/packages/website/docs/guide/concrete_syntax_tree.md b/packages/website/docs/guide/concrete_syntax_tree.md
@@ -29,7 +29,7 @@ There are two major differences.
 
 How to enable CST output?
 
-This feature is enabled when a parser extends the [CstParser class](https://chevrotain.io/documentation/11_0_2/classes/CstParser.html).
+This feature is enabled when a parser extends the [CstParser class](https://chevrotain.io/documentation/11_0_3/classes/CstParser.html).
 
 ```typescript
 import { CstParser } from "chevrotain";
@@ -45,7 +45,7 @@ class SelectParser extends CstParser {
 
 The structure of the CST is very simple.
 
-- See the full [CstNode type signature](https://chevrotain.io/documentation/11_0_2/interfaces/CstNode.html)
+- See the full [CstNode type signature](https://chevrotain.io/documentation/11_0_3/interfaces/CstNode.html)
 
 - Explore it by running the CST creation example in the [**online playground**](https://chevrotain.io/playground/?example=JSON%20grammar%20and%20automatic%20CST%20output).
 
@@ -238,7 +238,7 @@ as we would have to fully traverse a CstNode to understands its full location ra
 
 The feature for providing CstNode location directly on the CstNodes objects is available since version 4.7.0.
 Tracking the CstNodes location is **disabled by default** and can be enabled
-by setting the IParserConfig [nodeLocationTracking](https://chevrotain.io/documentation/11_0_2/interfaces/IParserConfig.html#nodeLocationTracking)
+by setting the IParserConfig [nodeLocationTracking](https://chevrotain.io/documentation/11_0_3/interfaces/IParserConfig.html#nodeLocationTracking)
 to:
 
 - "full" (start/end for **all** offset/line/column)
@@ -258,14 +258,14 @@ class SelectParser extends CstParser {
 }
 ```
 
-Once this feature is enabled the optional [location property](https://chevrotain.io/documentation/11_0_2/interfaces/CstNode.html#location)
+Once this feature is enabled the optional [location property](https://chevrotain.io/documentation/11_0_3/interfaces/CstNode.html#location)
 on each CstNode would be populated with the relevant information.
 
 Caveats
 
 - In order to track the CstNodes location **every** Token in the input Token vector must include its own location information.
 
-  - This is enabled by default in the Chevrotain Lexer, See [ILexerConfig.positionTracking](https://chevrotain.io/documentation/11_0_2/interfaces/ILexerConfig.html#positionTracking).
+  - This is enabled by default in the Chevrotain Lexer, See [ILexerConfig.positionTracking](https://chevrotain.io/documentation/11_0_3/interfaces/ILexerConfig.html#positionTracking).
     However, if a third party Lexer is used in conjunction with a Chevrotain Parser, the Tokens produced by such a lexer
     must include the relevant location properties to allow the chevrotain parser to compute the CstNode locations.
 
@@ -479,7 +479,7 @@ But what if we want **explicit** definitions for these data structures and APIs?
 
 - For example to easily implement our CST Visitors in TypeScript instead of over-using the `any` type...
 
-This capability is provided via the [generateCstDts](https://chevrotain.io/documentation/11_0_2/modules.html#generateCstDts) function.
+This capability is provided via the [generateCstDts](https://chevrotain.io/documentation/11_0_3/modules.html#generateCstDts) function.
 Which given a set of grammar `Rules` will generate the **source text** for the corresponding TypeScript signatures.
 
 For example, given the Parser rules for **arrays** in JSON.
@@ -515,7 +515,7 @@ export type ArrayCstChildren = {
 };
 ```
 
-Note that the [generateCstDts](https://chevrotain.io/documentation/11_0_2/modules.html#generateCstDts) function
+Note that the [generateCstDts](https://chevrotain.io/documentation/11_0_3/modules.html#generateCstDts) function
 only produces the **source text** of the TypeScript signatures, and it is the end-user's responsibility to save
 the contents to a file, see: minimal [generation script example](https://github.com/Chevrotain/chevrotain/tree/master/examples/implementation_languages/typescript/scripts/gen_dts_signatures.js).
 

diff --git a/packages/website/docs/guide/custom_token_patterns.md b/packages/website/docs/guide/custom_token_patterns.md
@@ -34,7 +34,7 @@ function. But with a small constraint.
 - A custom pattern should behave as though the RegExp [sticky flag](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/sticky) has been set.
   This means that attempted matches must begin at the offset argument, **not** at the start of the input.
 
-The basic syntax for supplying a custom pattern is defined by the [ICustomPattern](https://chevrotain.io/documentation/11_0_2/interfaces/ICustomPattern.html) interface.
+The basic syntax for supplying a custom pattern is defined by the [ICustomPattern](https://chevrotain.io/documentation/11_0_3/interfaces/ICustomPattern.html) interface.
 Example:
 
 ```javascript
@@ -62,7 +62,7 @@ createToken({
   pattern: { exec: matchInteger },
 
   // Optional property that will enable optimizations in the lexer
-  // See: https://chevrotain.io/documentation/11_0_2/interfaces/ITokenConfig.html#start_chars_hint
+  // See: https://chevrotain.io/documentation/11_0_3/interfaces/ITokenConfig.html#start_chars_hint
   start_chars_hint: ["1", "2", "3", "4", "5", "6", "7", "8", "9"],
 });
 ```
@@ -99,7 +99,7 @@ function matchInteger(text, offset, matchedTokens, groups) {
 
 A larger and non contrived example can seen here: [Lexing Python like indentation using Chevrotain](https://github.com/chevrotain/chevrotain/blob/master/examples/lexer/python_indentation/python_indentation.js).
 
-It is important to note that The matchedTokens and groups arguments match the token and groups properties of the tokenize output ([ILexingResult](https://chevrotain.io/documentation/11_0_2/interfaces/ILexingResult.html)).
+It is important to note that The matchedTokens and groups arguments match the token and groups properties of the tokenize output ([ILexingResult](https://chevrotain.io/documentation/11_0_3/interfaces/ILexingResult.html)).
 These arguments are the current state of the lexing result so even if the lexer has performed error recovery any tokens found
 in those arguments are still guaranteed to be in the final result.
 

diff --git a/packages/website/docs/guide/generating_syntax_diagrams.md b/packages/website/docs/guide/generating_syntax_diagrams.md
@@ -19,7 +19,7 @@ library by @tabatkins.
 
 ## Instructions
 
-Chevrotain provides the [**createSyntaxDiagramsCode**](https://chevrotain.io/documentation/11_0_2/modules.html#createsyntaxdiagramscode) API to generate the **html source code**
+Chevrotain provides the [**createSyntaxDiagramsCode**](https://chevrotain.io/documentation/11_0_3/modules.html#createsyntaxdiagramscode) API to generate the **html source code**
 of syntax diagrams. This html source code can then be used by an end user in either node.js or a browser:
 
 1.  By writing it directly to the disk in a pure node.js runtime scenario.