Sam Cao
I think the current behavior is to return `undefined`, and yes, it can throw an error instead.
A TSC based solution usually is 10x-20x slower than an SWC / esbuild based one. It might be worthy of checking [Run TypeScript Directly in Java](https://blog.caoccao.com/run-typescript-directly-in-java-82b7003b44b8) out.
That's not a problem. There are a lot of Minecraft users using Javet as well.
Yes, I met the same issue. Is it possible to set the line number of the first line?
Have you tried to write a custom module resolver? Node.js ESM in Javet is known to be problematic. You may ping me at discord for details.
I think that's a quite interesting feature request. It will take sometime to investigate if this feature could be implemented.
Thank you for the sharing. That's exactly one of the concerns I hold: It might not improve the performance in some common cases.
May I know which mode you were using? Both Node.js and V8 modes don't have the built-in support to importing from arbitrary resource because: 1. V8 is a pure script...
In Gradle, you get this out-of-box. Please review this [doc](https://www.caoccao.com/Javet/tutorial/basic/installation.html). ```kotlin import org.gradle.internal.os.OperatingSystem val os = OperatingSystem.current() val arch = System.getProperty("os.arch") val version = "4.1.5" val isI18n = false val...
I doubt that because i18n cannot be handled this way.