Erik LaBianca

A PR sounds good! I'm not sure I follow how replacing "yarn" or "npm" with "webpack" would work to download the project specific assets though? Will webpack downloading missing dependencies...

I'm running into this issue as well. I'm pretty sure when we initially implemented LibraryOnly the fastopt / fullopt outputs were wrapped in an IIFE. @julienrf do you happen to...

It appears as if the IIFE on commonjs modules disappeared in scala.js 0.6.16 -- see https://github.com/scala-js/scala-js/issues/2785 As a workaround, you can use Application mode with fullOpt, you'll just lose the...

I *think* the correct solution is to consume ES modules instead of CommonJS modules from scala.js, but I could be totally wrong on that. @sjrd would probably know if that's...

@sjrd is there some other path to getting an isolated module out of Scala.js? Re wrapping the entire file with the library ends up destroying the sourcemaps let alone the...

@sjrd webpack isn't involved here. In BundlingMode.LibraryOnly we extract the dependencies from the Scala.js output and use them to trick webpack into creating a bundle of all the dependencies, then...

After some further investigation, I think I have the path forward. @sjrd I'd appreciate your feedback on the approach. Net-net ES2015 modules are here. Scala.js can output them, and if...

After some further investigation, it doesn't look like webpack can emit an ES2015 module so we'd have to use rollup to create the library bundle. https://github.com/webpack/webpack/issues/2933

Thanks @sjrd, that's what I suspected. The trick with going direct ES-to-the-browser is going to be automating making the dependency tree available to the browser as ES modules -- I'm...

I've been thinking along the same lines. Webpack and the js ecosystem prefers to be the top level process, so we're always going to feel pain trying to wrap it...