| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
since the stdout will have the necessary information for debugging anyway
|
|\ |
|
| |
| |
| |
| | |
ModuleKinds (#212)
|
|/
|
|
| |
properly
|
|
|
|
|
|
|
|
|
| |
Specifically, fix 2 issues in order to better mirror the behavior of "sbt fullOptJS"
- Invoke the Google Closure Compiler after generating the optimized Javascript output
- Set scala.scalajs.LinkingInfo.developmentMode = false (and productionMode = true) when
building fullOpt in order to allow Scala.js code to distinguish between development
and production mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Adds Node.js configuration in ScalaJSModule.
* Adds Node.js configuration in ScalaJSModule test framework.
* Refactored ScalaJSBridge Node.js env creation.
* Readjusted ScalaJSBridge 0.6 formatting.
* Added Node.js config tests.
* Removed NodeJSConfig ScalaTest tests and improved log test conditions.
|
|
|
|
| |
Also disable ScalaJSModule#runMain, since the official Scala.js-SBT plugin does not support it and it requires an expensive re-linking every time it is run.
|
|
|
|
| |
scala.js run command
|
|
|
| |
fixes #102. Use scala js testing framework to launch tests
|
| |
|
|
|
|
| |
Removes a lot of useless folders and gives us a chance to exercise this simplified layout. Support for the SBT layout is still verified by our integration tests
|
|
- Update `build.sc`, `build.sbt` and `ci/` scripts
|