Domantas Petrauskas
Domantas Petrauskas
Providing plugin ID at runtime is not the same as dynamic configuration of the plugin, AFAIK.
Ideally this should just be configurable in settings, maybe with an upper bound to not bring down the server if someone decides to download a billion of puzzles.
This process is unfamiliar and - I got to be honest - a bit funky to me, I wonder if it can be modified somewhat to fit the tooling better....
> If you need non-bundled exported Scala.js components, then `@JSExportTopLevel` should be enough. Just to correctly myself, I should have just linked https://www.scala-js.org/doc/interoperability/export-to-javascript.html and https://www.scala-js.org/doc/project/module.html. Best course of actions might...
I totally understand your issue, but just to repeat https://github.com/ptrdom/scalajs-vite/issues/39#issuecomment-1930390189, I think you have both a bundler and a workspace issue, and this project should only be solving the former...
Sure, that seems like a reasonable feature to implement. Currently `viteCompile` task does the copying from `scalaJSLinkerOutputDirectory` to `viteInstall / crossTarget`. The way I see it the implementation can be...
I think nothing will need to be copied into this repo from 194 PR, just that once this repo implements necessary changes for plugin interface then users will be able...
Yes, very similar indeed.
I think the Akka gRPC projections depend on licensed dependencies provided by Akka - you need to add a custom resolver to sbt and register to get a token to...