Incremental bundling about scalajs-bundler HOT 7 CLOSED

One easy way to test in advance whether an AMD ModuleKind would work is to use a CommonJS-to-AMD converter, and time the results of working with the AMD module (discounting the time taken by the converter).

from scalajs-bundler.

Not sure webpack-dev-server would help because anyway the output of Scala.js is one module of several megabytes.

Another solution would be to have another kind of ModuleKind which would emit AMD modules so that there would be no need of bundling process (we would just need to transform the modules (once) into the AMD format).

from scalajs-bundler.

Some numbers.

Working with a 5k SLOC application, here are some timings when editing code and reloading the app:

Edit: more numbers!

from scalajs-bundler.

Another solution suggested on gitter: bundle all the dependencies and export them in a way that can be directly used by the output of Scala.js (so that this output doesn’t need to be processed by webpack).

from scalajs-bundler.

Have you looked into rollup instead of webpack? I've heard it's a lot faster.

from scalajs-bundler.

I will probably do some tests with rollup, yes.

from scalajs-bundler.

scala-js/scala-js#2175 (comment) implies rollup can take 1/4 the time webpack takes

from scalajs-bundler.