Andreas Woess
Andreas Woess
Solved by https://github.com/oracle/graal/commit/5539bb2187b15bbc1ba71628f4d45cb21d50d145.
The solution should be included in 22.3. We probably just forgot to mention it in the release notes.
If it's important to run those tests in raw mode, maybe using one of the built-in Error types (other than SyntaxError) would be the way to go then? (or including...
How would you pass that `ProxyObject` to JS so that it can be resolved by the module lookup? But my main question would be what can be achieved by such...
Indeed it was only working by accident. I, too, would suggest to use `Map`. We _could_ allow `CharSequence` as a Map key type (and treat it like `String`), but I'm...
I don't see where the `util` package is provided in your example.
> Doesn't `js.commonjs-core-modules-replacements` provide that? Only if you provide an explicit mapping, but it might still be found in `node_modules` anyway which I think is what happens in the working...
Yes, GraalJS can run in interpreter-only mode using the fallback runtime, by removing the truffle-runtime jars from the module (or class) path. For that, it's probably enough to just replace...
You can also run with the system property `truffle.UseFallbackRuntime` set to true, i.e.: `-Dtruffle.UseFallbackRuntime=true`. (You'll probably want to combine it with `-Dpolyglot.engine.WarnInterpreterOnly=false`.)
Confirmed. I think this was caused by the switch to thin language launchers. It was kind of working by accident before. You can work around it by doing the expansion...