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
We'd very much appreciate help on this. The "ground truth" for the webpack'd UMD distribution is actually a valid node module. So if you successfully manage to add build/packages/js/hcert as a dependency to your node project, let us know how you pulled it off, and we'll see what we can do. However, we targeted the browser and node was never a requirement, so we directly depend on quite some browserified libraries, which will almost certainly cause issues. "Fixing" this would require changes to the build process. There's probably a way to accomplish this, but this is a non-priority for us, so we are very hesitant to invest in this.
You can, of course, directly integrate the UMD module we currently provide with your node app (with all obvious drawbacks of this approach).
@JesusMcCloud Thanks for your explanation. We use JavaScript mainly for our API tests and hoped for a simple solution :).
We do not have resources to follow up right now, but I leave the issue open. Maybe someone else steps in.
Since https://youtrack.jetbrains.com/issue/KT-43237
is fixed (also for all our dependencies), we can drop the
workaround.
This also means that we could probably add a second JS target
without all the browserified node dependencies and directly
publish to npmjs.com in the future.
Hence, this paves the way to addressing #49.
Could you publish the JS library on npmjs.com or as GH package?
This would help a lot :).
CC: @mofobo-bit
The text was updated successfully, but these errors were encountered: