yalc
DevToys
yalc | DevToys | |
---|---|---|
7 | 53 | |
5,419 | 23,666 | |
- | 4.4% | |
1.1 | 9.4 | |
4 months ago | 7 days ago | |
TypeScript | C# | |
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.
yalc
-
Useful Javascript Monorepo Tools To Consider While Managing Multiple projects
Yalc
-
What are the not-so-obvious tools that you don't want to miss?
Yalc - Makes it easy to mock-publish NPM packages and try them in real projects before you publish a new version to NPM.
-
Share private NPM packages across projects
As well as yarn/npm link mentioned in another comment, https://github.com/wclr/yalc can help with some of this, depending on your workflow/how much you're doing this.
-
How do you debug a library written in Typescript in a React app using it?
Ah okay, that's much easier. Clone the project repo, make your changes and build the library, then in the react app, either add the local project directory as a dependency, or use something like yalc to add the locally built dependency. This will allow you to use the local copy of the library instead.
-
We Halved Go Monorepo CI Build Time
Lets look at a concrete example and then maybe we can discuss alternatives.
In this particular case, I would respond with the following:
1. I don't see why this is a problem. Have an "open PRs" link in the onboarding handbook that gives you a view of pull requests from all repos in the organization. GitHub automatically shows you notifications from all repos.
- Have a (Grafana) dashboard where you can see the latest / newest stuff. Use standard GH tools you use for OSS, such as follows etc to keep up.
2. Don't prematurely split into multiple libraries. "No monorepo" doesn't mean not having poly-package repos. It means thinking what the sensible API boundary is - treating your projects as you would treat library development. In this case a separate repo with lib3, lib2 and lib1 sounds like a good way to go - at most one repo per orthogonal internal framework (e.g. core-react-components).
3. Help other teams upgrade. If you are responsible for repo A, once you publish a new version and tag it with semver appropriately, use the dashboard to look at your dependants and work with them (or rather, for them) to upgrade. Think of your dependants as internal customers, and make sure you add enough value for them to justify the upgrade effort.
4. There are other alternatives to `npm link` e.g. see `yalc` https://github.com/wclr/yalc
-
Using local NPM packages as dependencies with yalc
yalc makes it easy to use locally-developed packages in other projects. It has some other useful options that I didn't mention here; read more about them on the project's README. Hopefully, this helps you get started developing with local packages––good luck!
-
Where do I store components I need to use in multiple React apps that are being built simultaneously?
You can also use yalc which is like an npm store on your engine.. https://github.com/wclr/yalc
DevToys
- Set Up MacOS for Development Productivity
-
Selfhosted Prettyprint/Encoder/Decoder/Validator/Utility thing?
https://devtoys.app/ Windows only though.
-
I've got several good ones bookmarked.
Strictly speaking, DevToys isn't an online builder.
-
Bar the WIN UI Gallery Example what other projects stand out as a learning resource
Here's a few: - MVVM Toolkit sample app - Ambie - Brainf*ck# - DevToys
-
What are the not-so-obvious tools that you don't want to miss?
Also recently came across DevToys which has a lot of handy tools in a clean interface
-
Self-hosted alternative to jwt.io
Check out https://github.com/veler/DevToys
-
Anyone know where to find a good sample WPF MVVM application?
If it helps, here's also a bunch of open source MVVM apps you can look at for inspiration (again, they're UWP, but if you ignore the XAML differences all the rest is just plain MVVM): - https://github.com/jenius-apps/ambie - https://github.com/Sergio0694/Brainf_ckSharp - https://github.com/veler/DevToys
-
Apps that should be paid, but are not (Part 4)
Replacement for tools like devutils.com and devtoys.app
- New update of DevToys - A Swiss Army knife for developers
-
[UWP App] New update of DevToys - A Swiss Army knife for developers
Check out https://devtoys.app
What are some alternatives?
verdaccio - 📦🔐 A lightweight Node.js private proxy registry
DevUtils-app - All-in-one Toolbox for Developers. Native macOS app.
renovate - Universal dependency automation tool.
CyberChef - The Cyber Swiss Army Knife - a web app for encryption, encoding, compression and data analysis
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
Notepads - A modern, lightweight text editor with a minimalist design.
breakpad - Mirror of Google Breakpad project
GenshinLyreMidiPlayer - Genshin Impact Windsong Lyre, Floral Zither, & Vintage Lyre MIDI auto player in Modern Mica UI. Supports MIDI instruments & Playlist controls.
rumps - Ridiculously Uncomplicated macOS Python Statusbar apps
Monaco Editor - A browser based code editor
bitbar - Put the output from any script or program into your macOS Menu Bar (the BitBar reboot)
MicaForEveryone - Mica For Everyone is a tool to enable backdrop effects on the title bars of Win32 apps on Windows 11.