superdiff
monorepo.tools
Our great sponsors
superdiff | monorepo.tools | |
---|---|---|
5 | 26 | |
433 | 278 | |
- | 3.2% | |
5.2 | 2.7 | |
28 days ago | 4 months ago | |
TypeScript | TypeScript | |
- | 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.
superdiff
-
Superdiff has reached 377 GitHub stars thanks to you. Here are the latest enhancements.
A few weeks ago, I shared Superdiff, a library that compares two arrays or objects and returns a full diff of their differences in a readable format, on this sub. The project has gained some traction, with 377 GitHub stars. Thanks to user feedback, Superdiff now offers significant improvements since last time: - Supports diff between arrays with duplicate values - Provides the option to consider two arrays with the same values but in a different order as equal - Allows you to filter the diff output by state, with full control over nested properties; diff readability has never been better. - Fixes remaining edge cases, with more tests. Source code
-
[AskJS] What do you use for image tracking? I was wondering, with all the libraries and frameworks out there, what do you use for image tracking with JavaScript
For object tracking, you could look at Superdiff. For image tracking, img-diff-js
- Superdiff: compare objects and arrays with readable diffs
-
Introducing Superdiff: compare objects and arrays with readable diffs
Examples and documentation can be found here. Here is also the source code.
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?
jsondiffpatch - Diff & patch JavaScript objects
ember-react-example - Example of invoking React components from an Ember app.
react-diff-viewer - A simple and beautiful text diff viewer component made with Diff and React.
nx-dotnet
quantified-self - Compare files from various activity trackers
large-monorepo - Benchmarking Nx and Turborepo
what-code-is-faster - A browser-based tool for speedy and correct JS performance comparisons!
bleep - A bleeping fast scala build tool!
css-in-js - A thorough analysis of all the current CSS-in-JS solutions with SSR & TypeScript support for Next.js
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
nx-recipes - 🧑🍳 Common recipes to productively use Nx with various technologies and in different setups. Made with ❤️ by the Nx Team
gradle-code-style-plugin-example - Custom Gradle Plugin for Unified Static Code Analysis