Julien Richard-Foy
Julien Richard-Foy
@easel But then in case your backend is written in Scala as well (which I guess is often the case if the frontend is in Scala) you have to define...
Interesting! Do we need to provide some sort of integration (ie, we would replace the bundling part currently done by webpack with something that uses esbuild)? Or should we remove...
> Should we consider removing support for some of the older versions? This is fine by me, but I would like to hear from other users of scalajs-bundler :)
Thanks for reporting. The bundle files are returned by the [`webpack` command](https://scalacenter.github.io/scalajs-bundler/api/latest/index.html#scalajsbundler.sbtplugin.ScalaJSBundlerPlugin$$autoImport$). I think the right implementation would be something like the following: ~~~ scala fastOptJS in testHtmlFastOpt in Test...
What do you mean by “the website”?
That would be great if you could directly fix the plugin :) You should add it to [this list](https://github.com/scalacenter/scalajs-bundler/blob/master/sbt-scalajs-bundler/src/main/scala/scalajsbundler/sbtplugin/ScalaJSBundlerPlugin.scala#L339) (and you should add a similar setting for `testHtmlFullOpt`, I think)...
@raquo Are you using the `testHtmlFastOpt` task? Just running the tests with `test` should work if you added `requiresDOM in Test := true` to your build.
It might be the same issue, indeed… This would require a bit of investigation.
This will probably require adaptations on the Scala.js side because it is currently not possible to emit several modules from a Scala.js project.
Hi, no I have no better suggestion :(