From 11f16d7e5ce9f44ca26bc40cb0dc8c059aeb5324 Mon Sep 17 00:00:00 2001 From: hildjj Date: Mon, 26 Feb 2024 16:16:52 +0000 Subject: [PATCH] deploy: ab63796bc9c74a7930ee628f2414eda54ed364ae --- documentation.html | 13 +++++++++++-- index.html | 2 +- js/benchmark-bundle.min.js | 4 ++-- js/examples.js | 2 +- js/test-bundle.min.js | 4 ++-- vendor/peggy/peggy.min.js | 4 ++-- 6 files changed, 19 insertions(+), 10 deletions(-) diff --git a/documentation.html b/documentation.html index 944c1af0..609d28e3 100644 --- a/documentation.html +++ b/documentation.html @@ -778,8 +778,17 @@

Importing External Rules

grammar, NOT the source. Grammars MUST be compiled by a version that supports imports in order to be imported. Only rules that are allowed start rules are valid. It can be useful to specify - --allowed-start-rules \* in library grammars. All of the - following are valid:

+ --allowed-start-rules * (with appropriate escaping for + your shell!) in library grammars. Imports are only valid in output + formats "es" and "commonjs". If you use imports, you should use + { output: "source" }; the default output of "parser" will + call `eval` on the source which fails immediately for some formats + (e.g. "es") and will not find modules in the expected places for others + (e.g. "commonjs"). The + from-mem project is + used by the Peggy CLI to resolve these issues, but note well its + relatively severe limitations.

+

All of the following are valid: