paulbartrum

The only straightforward way to keep the debugging support is to stick with the 3.1.0 version I'm afraid. Sorry!

require() is a node.js-specific thing I think. There's a standard (ECMAScript) replacement called "import" but Jurassic doesn't support that either :-(

I removed the strong name on purpose as part of switching to .NET standard. My reasoning was based on this article: https://www.pedrolamas.com/2016/03/01/still-strong-naming-your-assemblies-you-do-know-its-2016-right/ What's your need for this feature?

Could you not just use this? ```c# scriptEngine.SetGlobalValue("window", scriptEngine.Global); ```

Well, you'd need to modify the lexer to recognise `->` as a token, then modify the compiler to parse that token and produce a `FunctionExpression`. The hard part is likely...

If you just want to compile some javascript once, and then run it multiple times, you can use the `ScriptEngine.Compile()` method. If you want something that persists across application restarts,...

`EnableDebugging = true` switches to an alternate way of generating the dynamic in-memory assembly. Technically it uses `AppDomain.DefineDynamicAssembly` rather than the default, which is to use the somewhat faster `DynamicMethod`...

Ugh, I told you this was hacky :-/ The `scope` parameter is used to manage variable scopes and lifetimes -- try calling this method to get a suitable one: `Jurassic.Compiler.ObjectScope.CreateRuntimeScope(null,...

It's likely the code is assuming that you can't run any compiled JS code without first compiling it. As a workaround, you could try compiling something prior to running the...

Also I'm happy to do a PR if I can get some guidance on what approach to take with the native DLLs.