Julien Richard-Foy
Julien Richard-Foy
Hello @evbo, I currently don’t do code splitting with scalajs-bundler. Someone needs to pioneer this area!
Indeed, I think checking that `scalaJSModuleKind` has been set to something **different than `ModuleKind.NoModule`** should work. Ideally, we could also check that the webpack version used does support ES modules.
Awesome, thanks for investigating! > Are there other areas to check Maybe running tests, and running tests that use the DOM.
Hello! Unfortunately, this project lacks maintainers. Something you could do to help this move would be to locally test the PR that has been open, to fix the git conflicts,...
Maybe we can close this issue then?
Can you also confirm the reproduction scenario?
Maybe using this loader would solve the problem? https://github.com/aappddeevv/scalajs-friendly-source-map-loader
scalajs-bundler uses the output of Scala.js. If you have a multi-module build, then scalajs-bundles uses the .js file that results from the linking of all the modules. What’s the problem...
I used to work on a multi-(sbt)-modules project, where module dependencies were expressed using `dependsOn`. I didn’t have the problem you mention: IntelliJ was able to resolve the code coming...
Your backend has to use the output of the `webpack` task applied to your frontend. Or you can just use [sbt-web](https://scalacenter.github.io/scalajs-bundler/getting-started.html#sbt-web).