creating new builds with vite has this nice feature where you select from common frameworks. test frameworks and if you want a TypeScript project. I think this would be a really cool feature to have.
These templates would have to build on some common Scala use-cases.
Some common template ideas:
Web
- Http4s
- Cask
- Tapir (w/o backend?)
- Smithy4s
- ZIO-http
Frontend
Scala-native
Fullstack
- Maybe too many opinions here
This kind of thing would be an adoption booster as it would get people into coding much faster. We could reuse sbt g8 templates and import the sbt builds, but I don't think this would provide a good experience. Rather we could set up some common interface for adding a template. The issue with keeping the templates in bleep is that the maintenance burden is on bleep maintainers. I think identifying the most commonly used project structures and adding those would be important.
Personally I think the benefits would outweigh the costs on this one if adoption is a long term goal.
creating new builds with vite has this nice feature where you select from common frameworks. test frameworks and if you want a TypeScript project. I think this would be a really cool feature to have.
These templates would have to build on some common Scala use-cases.
Some common template ideas:
Web
Frontend
Scala-native
Fullstack
This kind of thing would be an adoption booster as it would get people into coding much faster. We could reuse sbt g8 templates and import the sbt builds, but I don't think this would provide a good experience. Rather we could set up some common interface for adding a template. The issue with keeping the templates in bleep is that the maintenance burden is on bleep maintainers. I think identifying the most commonly used project structures and adding those would be important.
Personally I think the benefits would outweigh the costs on this one if adoption is a long term goal.