sbt VS scala-trace-debug

NOTE: I won’t mention SBT and Leiningen here because, with all due respect, they are niche build tools. I also won’t discuss Kobalt for the same reason (besides, it’s no longer actively maintained). Additionally, I won’t touch upon Bazel and Buck in this context, mainly because I’m not very familiar with them. If you have insights or comments about these tools, please feel free to share them in the comments 👇

Sbt has the primitives that would allow that, but this would change the semantics of the test task. See also testQuick and https://github.com/sbt/sbt/issues/6292

If I use IntelliJ then apparently sbtn is not supported and they don't bother with Scala-CLI or Coursier.

Version 1.3.13 has a size of 1.17 MB in zip

See scala-xml 2.x mega tracker on plugin ecosystem conflicts.

This is under discussion at https://github.com/sbt/sbt/issues/6997

See https://github.com/playframework/playframework/issues/10572 and https://github.com/sbt/sbt/issues/6235 for more details and context.

BTW, if you're curious, it appears OP is using this: https://github.com/sbt/sbt/releases/tag/v1.6.2 Pretty sure one of the executables is doing ANSI colours.

If you see the progression of documentation changes over the years pushing people towards multi-project style, and issues like https://github.com/sbt/sbt/issues/6217, hopefully you'd see that I've really tried to encourage people to use multi-project style from the get go.

Fyi in case anyone is curious, sbt is fully removing log4j going forward: https://github.com/sbt/sbt/pull/6726

If you're not sure what you want to do maybe build your own sample site from a "starter" like https://github.com/microsoft/TypeScript-Node-Starter (this one uses TypeScript which is JavaScript with types added) or https://github.com/sahat/hackathon-starter (this one uses plain old JavaScript without types). I personally deploy to https://www.heroku.com/ because it's less complicated than deploying to AWS or Google Cloud but more businesses deploy to AWS than Heroku so learning AWS and having the AWS services you use to build and deploy your app as skills on your resume would probably make your resume look better to companies than just saying you know Heroku. If you want to copy off me (don't make and use an exact copy) my sample app deployed to Heroku has its code at https://github.com/JohnReedLOL/TypeScript-Node-Starter and the site is at https://sea-air-towers.herokuapp.com/ (I pay Heroku $7 a month for hosting). It's good to have a link to a sample app and link to the code for your sample app on your resume, just make the README.md file on GitHub look good so people can look at it and know what your app does. I have a software library with a much better looking README.md file at https://github.com/JohnReedLOL/pos