Jonathan Gilbert

Whilst I can understand the desire for some kind of persistence between script changes, I don't agree that this should be the default like you are suggesting in the above...

@FSeidinger if you are creating a specific variable to hold the state (`globalScope`) then I have no problem with you suggestion in principal. I do agree with @rkoshak that it...

> A quick example would be really really really appreciated. @rkoshak when I said that "It's incredibly easy to write" I actually meant in Java, not Javascript. It's a single...

You don't actually need to interact with any classes, you just need to register a class with OSGi that implements `ScriptExtensionProvider`. OSGi will ensure that the rest works. The primary...

@J-N-K tbh I have not been very careful with naming in the past because: - I personally always explicitly import everything as I've had huge issues in the past with...

Looking at the doc for GraalJS, it states that you can use either the root or node_modules folder for `js.commonjs-require-cwd`. I agree with you that it probably makes more sense...

> I agree with you, this could be a valid option, but I think this is not a simple solution or? Or is that working out-of-the box with the GraalVM...

> @jpg0 If you agree I would start with a first try or do you have already other plans? You can start, however I think that it's good to decide...

This isn't quite what I meant, as I was assuming a `package.json` in the root folder, which would point at the scripts to load. So in your example, either the...

My view has always been the same, which is that we should leave the execution context for scripts as close as possible to their standard (non openHAB) environment. It's interesting...