You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pulling J4TS into my project as a Maven dependency, and it works fine* as long as I use JSweet with module=none. If I turn on module=commonjs or module=es2015, the errors from the transpiler are very different, as if it couldn't see J4TS at all. Is there something else I need to do so that the J4TS dependency works with module=commonjs?
I saw somewhere in a README here that J4TS is "module compatible". It looks like that means it is published on NPM, so I suppose a commonjs module. I can see how I could benefit from that in my client build, but that doesn't help me transpile with J4TS.
I should note, I did find the language spec section on modules, but that seems to apply only to the "def" package for bindings, and it is not clear whether it addresses compile-time dependencies at all.
*I do get some errors about java.util.StringTokenizer, which now seem odd, since I see that StringTokenizer is part of J4TS.
The text was updated successfully, but these errors were encountered:
Similar to what you describe, I can build individual files and make a bundle, but if I use the es2015, I suddenly get hundreds of errors, e.g. Cannot find name 'ArrayList'.
I'm pulling J4TS into my project as a Maven dependency, and it works fine* as long as I use JSweet with module=none. If I turn on module=commonjs or module=es2015, the errors from the transpiler are very different, as if it couldn't see J4TS at all. Is there something else I need to do so that the J4TS dependency works with module=commonjs?
I saw somewhere in a README here that J4TS is "module compatible". It looks like that means it is published on NPM, so I suppose a commonjs module. I can see how I could benefit from that in my client build, but that doesn't help me transpile with J4TS.
I should note, I did find the language spec section on modules, but that seems to apply only to the "def" package for bindings, and it is not clear whether it addresses compile-time dependencies at all.
*I do get some errors about java.util.StringTokenizer, which now seem odd, since I see that StringTokenizer is part of J4TS.
The text was updated successfully, but these errors were encountered: