Update sbt-resource-management or abandon? about sbt-resource-management HOT 2 OPEN

There's definitely a tradeoff here. My short assessment is that it will probably take somewhat less time to adapt this to latest sbt than to move a whole setup to a newer JS packager. The upside of a newer JS packager is the potential to leverage things like TypeScript directly in the build pipeline (though that could also be added here).

Long term there are gains to be had from using what the JS community is using. Shorter term it's probably easier to port this.

That said, I seem to recall there were some major API changes in sbt, so you could be looking at a bunch of spelunking.

from sbt-resource-management.

Thanks for that. Have to pivot to other tasks but when I circle round again I'm going to work on adapt this to the latest sbt 'cause it's less new stuff and, ergo, less moving parts.

I'll post again.. or maybe open a PR! 😲

from sbt-resource-management.