scala-trace-debug VS Scapegoat

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

I've since figured this out (Scapegoat/FinalModifierOnCaseClass and WartRemover/FinalCaseClass). I plan to add it to the next version of the article.

scapegoat, but I am biased because I have contributions to it.

The support for scala 3 has been requested a while ago: https://github.com/scapegoat-scala/scapegoat/issues/521 but the original author has stepped down as a maintainer https://github.com/scapegoat-scala/scapegoat/issues/567 and recently most of the changes are just dependency updates.