Julien Richard-Foy

Restrict the scope of this project

13

I believe we have too many extension points in this plugin (`webpackNodeArgs`, `npmExtraArgs`, `additionalNpmConfig`, `webpackDevServerExtraArgs`, `webpackExtraArgs`, `yarnExtraArgs`). I’m wondering if that’s a sign that the plugin is not at the...

npmResolutions doesn’t work well with npmDevDependencies

3

You might get incompatible resolutions between dev dependencies and dependencies. Workaround: ~~~ scala npmResolutions in Compile := { (npmDependencies in Compile).value.toMap ++ (npmDevDependencies in Compile).value.toMap } ~~~

The documentation [clearly says](https://scalacenter.github.io/scalajs-bundler/reference.html#bundling-mode-library-only) that the `LibraryOnly` bundling mode should not be used with `fullOptJS`. We should also print a warning when this case is detected.

Workaround: ~~~ scala webpackDevServerExtraArgs := Seq("--lazy", "--inline") ~~~

Export Scala.js projects as regular npm packages

4

Thus we could get rid of the `npmResolutions` machinery.

This is more a discussion than an issue, I would like to know what is the versioning scheme used by the library. For the record, I recommend declaring it in...