monorepo.tools
degit
monorepo.tools | degit | |
---|---|---|
26 | 22 | |
278 | 6,656 | |
1.4% | - | |
2.7 | 0.0 | |
4 months ago | 3 months ago | |
TypeScript | JavaScript | |
MIT License | 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.
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
degit
-
CMake and Git Submodules: More Advanced Cases
But what I'd like to do at this point to tie a bow on the whole thing, once you've made any customizations you feel necessary, is commit the whole thing as a degit template. This will help you reuse your template across many happy projects in the future!
-
Building a multilingual NextJS app using the new app directory
The easiest way to follow this guide is to degit a Nextjs boilerplate.
-
What do you use to easily setup new projects?
There's a tool for history-less cloning: https://github.com/Rich-Harris/degit
-
Add an Options Page to Chrome Extension
The easiest way is to use degit.
-
Invoking React components from your Ember apps
Here I am using degit to bootstrap our Ember app since the ember-cli doesn't allow you to create a new Ember app in the name of app.
-
Advice on migrating from multirepo to monorepo
Instead of starting from the idea of adopting a monorepo, you probably want to start from your pain points and work backwards from there. Standardizing on initial setup can be done w/ scaffolding tools (e.g. degit). Standardizing on configuration can be done w/ libraries (we do this for eslint, jest, etc). After-the-fact alignment can be done w/ codemods (e.g. jscodeshift) and PR tracking tools (IIRC sourcegraph has an offering like this).
-
Apexlang: Project Templates with Code Generators
Tools like yeoman, degit, and cargo generate kept me happy for years. They add basic templating capabilities to the standard git clone but they stop there. You’ll be hard pressed to find tools that go beyond setting up a directory structure.
- How do I preview a front-end project on Github without downloading the repo and setting up a local server (at least not manually)?
- Svelte - The First Four Magic Words
-
Create Beautiful Charts with Svelte and Chart js
You could use codesandbox for your initial setup or create a local svelte application using the degit tool. Open a new terminal and run the following command:
What are some alternatives?
ember-react-example - Example of invoking React components from an Ember app.
npx - npm package executor
nx-dotnet
Svelte - Cybernetically enhanced web apps
large-monorepo - Benchmarking Nx and Turborepo
yeoman - Yeoman - a set of tools for automating development workflow
bleep - A bleeping fast scala build tool!
svelte-component-ts
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Visual Studio Code - Visual Studio Code
nx-recipes - 🧑🍳 Common recipes to productively use Nx with various technologies and in different setups. Made with ❤️ by the Nx Team
template - Template for building basic applications with Svelte