Christian Wirth

Hi @Ivan-Kouznetsov thanks for your benchmarks, they provide relevant insight! And they show the fundamental misconception, which is > after many iterations of the same task 1000 iterations of something...

Hi, thanks for your suggestion. That seems to be a reasonable extension, we might have to add it behind a flag in order to stay compatible. Sounds like something a...

Hi moayman, thanks for your request. We inherited that limitation from Nashorn as we are reusing their parser. Lifting this limit might be possible with some effort, however, it is...

Hi moayman, > Thanks for letting me know about the load method. Umm, I though have a question. The JS file I am trying to use is basically a one...

@moayman it is definitly possible to lift the limitation. This requires to change how tokens are stored in the parser. We are happy to receive contributions that improve the parser...

Hi @slippycheeze thanks for your report. All the commands you report work fine for me, on Linux. I can globally install npm modules without problems (I regularly do, e.g. `jsvu`)....

> I'm also having the same issue. Global packages (installed using `npm install -g`) are not linked to `$PATH` in graalvm-nodejs. GraalVM usually does not put itself on the path....

Hi @slippycheeze ok, I now see your point. The directory is not created automatically by GraalVM; it is however created once needed, i.e. when you install something globally. Thus, we...

Hi @slippycheeze oh, thanks, I missed the `outdated`, only tried with `npm root` or installing a global package. I don't think we have `npm outdated` in our test scripts. Will...

Hi, thanks for bringing this up. We seem to have too strict checks for certain arguments ("VM config values" in the error message) that keep changing across JDK versions. We...