sbt
monorepo.tools
Our great sponsors
sbt | monorepo.tools | |
---|---|---|
20 | 26 | |
4,755 | 278 | |
0.4% | 3.2% | |
9.1 | 2.7 | |
5 days ago | 4 months ago | |
Scala | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sbt
-
Declarative Gradle is a cool thing I am afraid of: Maven strikes back
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 👇
-
Øyvind Berg and John De Goes discuss Bleep, the new config-as-data build tool
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
-
Scala Center Roadmap for 2023 and Beyond
If I use IntelliJ then apparently sbtn is not supported and they don't bother with Scala-CLI or Coursier.
-
The size of sbt became big
Version 1.3.13 has a size of 1.17 MB in zip
-
sbt 1.8.0 released
See scala-xml 2.x mega tracker on plugin ecosystem conflicts.
-
sbt 1.7.3 released
This is under discussion at https://github.com/sbt/sbt/issues/6997
-
Make your zip packages for lambdas (and many more use cases) idempotent with a zip-drop-in replacement
See https://github.com/playframework/playframework/issues/10572 and https://github.com/sbt/sbt/issues/6235 for more details and context.
-
How do i stop git bash from showing the time taken for each command
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.
-
simplifying sbt with common settings
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.
-
sbt 1.5.7 released
Fyi in case anyone is curious, sbt is fully removing log4j going forward: https://github.com/sbt/sbt/pull/6726
monorepo.tools
-
OneRepo: JavaScript/TS monorepo toolchain for safe, strict, fast development
I'm surprised this isn't getting any attention. Reading the docs, sounds very promising, thanks for creating this! I see Nx, Turbo and Moon being mentioned in passing in [Alternatives & pitfalls](https://onerepo.tools/concepts/why-onerepo/#alternatives--pi...), but a more in-depth comparison would be interesting. At least something that could be a column in the table at the bottom of [monorepo.tools](https://monorepo.tools/#tools-review).
-
Josh: Just One Single History
> I don't think anyone coming from a multi-repo world really understands the full implications of a monorepo until they've worked in a large scale one
That's entirely fair. My sole experience is the one black-sheep monorepo at my own relatively-recently joined company, which is nowhere even close to approaching true large scale.
Genuine question, though - what _are_ the advantages, as you see them (you didn't explicitly say as much, but I'm reading between the lines that you _can_ see some)? Every positive claim I've seen (primarily at https://monorepo.tools/, but also elsewhere) feels either flimsy, or outright false:
* "No overhead to create new projects - Use the existing CI setup" - I'm pretty confident that the amount of DX tooling work to make it super-smooth to create a new project is _dwarfed_ by the amount of work to make monorepos...work...
* "Atomic commits across projects // One version of everything" - this is...actively bad? If I make a change to my library, I also have to change every consumer of it (or, worse, synchronize with them to make their changes at the same time before I can merge)? Whereas, in a polyrepo situation, I can publish the new version of my library, and decoupled consumers can update their consumption when they want to
* "Developer mobility - Get a consistent way of building and testing applications" - it's perfectly easy to have a consistent experience across polyrepos, and or to have an inconsistent one in a monorepo. In fairness I will concede that a monorepo makes a consistent experience more _likely_, but that's a weak advantage at best. Monorepos _do_ make it significantly harder to _deliberately_ use different languages in different services, though, which is a perfectly cromulent thing to permit.
-
What is the difference between monoliths, microservices, monorepos and multirepos?
The section on what monorepo tools should provide is useful if you are planning to set up an enterprise-level monorepo.
-
Contributing to the cause: doing it the open-source way
The next step would be to familiarize yourself with the codebase. Most of the repositories use monorepos for organizing and managing their code. A rule of the thumb here would be to make yourself familiar with what component lies in which place. It is next to impossible to understand the entire codebase at once. For starters, you can:
-
Joys and woes of monorepos
Monorepos are a great concept, especially in environments like Node.js which encourage having many small packages.
- Desenvolvendo APIs fortemente tipadas de ponta a ponta com tRPC
-
Confuse about TypeScript setup in monorepo
You might want to use monorepo tooling like NX, Lerna, or Turborepo to guide you. https://monorepo.tools/ has a list of tools.
- Monorepo Explained
-
Øyvind Berg and John De Goes discuss Bleep, the new config-as-data build tool
This explains it really well: https://monorepo.tools/
-
Good monorepo tooling
Have a look here to get some good context around monorepo tooling and if it’s something you actually need and want to do - https://monorepo.tools Some of the monorepo tooling can be a steep learning curve so you want to really think about the problem you are trying to solve and whether the effort will be worth it
What are some alternatives?
Mill - Your shiny new Java/Scala build tool!
ember-react-example - Example of invoking React components from an Ember app.
dotty - The Scala 3 compiler, also known as Dotty.
nx-dotnet
bloop - Bloop is a build server and CLI tool to compile, test and run Scala fast from any editor or build tool.
large-monorepo - Benchmarking Nx and Turborepo
scalafmt - This repo is now a fork of --->
bleep - A bleeping fast scala build tool!
Metals - Scala language server with rich IDE features 🚀
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Wartremover - Flexible Scala code linting tool
nx-recipes - 🧑🍳 Common recipes to productively use Nx with various technologies and in different setups. Made with ❤️ by the Nx Team