sjrd on 0.6.x
Remove dead code: specific coll… Adapt the signature of `js.Arra… Merge pull request #3554 from s… (compare)
sjrd on master
Fix analyzer cycle detection to… Add toString methods to analyze… Do not provide linked ClassInfo… and 1 more (compare)
sjrd on master
Remove Logger.success It is un… Make level helpers final Clean-up ScalaConsoleLogger cod… and 1 more (compare)
scalaJSLinkerConfig.withBatchMode(true). What does this do/change
github.com/objektwerks/scalajs.pool. Some time ago, js-opt.js and shared-opt.js files were generated from a fullOptJS. That has changed with 1.5 and the module linking feature.
I am building for a while my scala-js application at runtime because my application is pluggable. I have to be abble to add plugins at runtime or restart the application including new plugins. It use the Linker methods to achieve this (see sources here: https://github.com/openmole/openmole/blob/13-dev/openmole/gui/server/org.openmole.gui.server.jscompile/src/main/scala/org/openmole/gui/server/jscompile/JSPack.scala).
Until now, I dealt with my js lib dependencies by hand, merging js deps in a big js file. But I had often js loading or depencies resolution issues. So I try to use webpack, which is pretty straight forward when everything is compiled and linked from the sbt file. But not really in my case.
My idea was to
1) fastOptJS / webpack an empty project, which depends on the same dependencies as my application (and just calling a couple of fake methods to trigger webpack), so that I get a js file resolving all the js dependencies I need for my main project,
2) build my application with fastOptJS (but with no wepback resolution)
3) merge both js in a big one.
4) compress this big js file (if it is possible afterwards)
The problem is that the main method of the main application is not recognized any more, the html body tag remains empty and nothing happens when the html is run.
Any idea on how to solve my problem ? Is the way I do seems to be the good one ?