Error using online Peggy - Can't find variable: util

[dselman]

When I use a parser within the Peggy online editor the parser displays an error:

Can't find variable: util

The same parser works when used from the command line or in a Node.js application.

The web-browser (latest Safari) displays the following two error messages in the console:

SyntaxError: Invalid regular expression: invalid group specifier name
TypeError: undefined is not an object (evaluating 'ann.from.line')

To reproduce

1. Copy the peg grammar: https://github.com/accordproject/concerto/blob/main/packages/concerto-cto/lib/parser.pegjs
2. Paste the grammar into the editor and then type the following input text (which is valid and should create an AST):

namespace test

3. The error Can't find variable: util appears below the parser input window.

[Mingun]

Doesn't reproduced for me. What exactly online editor did you mean? https://peggyjs.org/online? I tried to paste https://raw.githubusercontent.com/accordproject/concerto/cd9edf745a85f6b7fec818b700810a3a9f5bee0a/packages/concerto-cto/lib/parser.pegjs an the parser was generated without errors. Input namespace test parsed as:

{
  '$class': 'concerto.metamodel@1.0.0.Model',
  decorators: [],
  namespace: 'test',
  imports: [],
  declarations: []
}

[dselman]

Doesn't reproduced for me.

Interesting! I just tried it in Chrome and it works, so it appears to be an issue specific to Safari. I am using Safari Version 16.2 (18614.3.7.1.5).

[hildjj]

I can reproduce this in Safari. This looks to be an error in node-inspect-extracted. I'm going to try updating to the latest version of that package first, then see if there is still a problem.

[hildjj]

This should be fixed in Safari 16.4 according to this. I think maybe we should just test for util being available, and fall back on console.log("%O", result) for those that have broken browsers.

[hildjj]

OK, take a look at the pretty awful hack that is #372. I'd rather not change the offending line in node-inspect-extracted for two reasons: capturing the intent of the negative lookbehind adequately will be a little tough, and b) I'm trying to keep that code as close to nodejs source as possible.

[Mingun]

I forgot to mention, that I've checked on Firefox 110.0.1, but I also use the old Firefox ESR 52.9.0 because of its plugins, and this error affects it also (of course)