yalc
barrier
yalc | barrier | |
---|---|---|
7 | 616 | |
5,419 | 26,181 | |
- | 1.1% | |
1.1 | 0.0 | |
4 months ago | about 1 year ago | |
TypeScript | C | |
MIT License | GNU General Public License v3.0 or later |
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
barrier
-
Show HN: Multi-monitor KVM using just a USB switch
For software KVM you can use https://github.com/debauchee/barrier
I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)
- Barrier: Open-Source KVM Software
- Hrvach/Deskhop: Fast Desktop Switching Device
-
Wayland vs. X – Overview
libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?
For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through
And for host systems, it looks like xev only logs input events when the window is focused.
Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?
With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.
Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier
libei:
-
KVM Switch for Gaming and WFH
I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.
-
Autoswap Keyboard Layouts based on Operating System
Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...
-
Alternative solution to expensive KVM - Auto Monitor Input Switcher
Barrier appears to handle PC switching only for the keyboard and mouse.
-
IT/programming multi-monitor setup? (coming from 6x old 21" square)
Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.
- Linux VNC viewer not displaying MacOS with multiple desktops (single monitor)
-
Talon Voice in Visor?
Barrier is a free and open source alternative.
What are some alternatives?
verdaccio - 📦🔐 A lightweight Node.js private proxy registry
synergy-core - Open source core of Synergy, the cross-platform keyboard and mouse sharing tool (Windows, macOS, Linux)
renovate - Universal dependency automation tool.
input-leap - Open-source KVM software
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
hidusbf - USB Mice Overclocking Software (for Windows)
breakpad - Mirror of Google Breakpad project
OSX-KVM - Run macOS on QEMU/KVM. With OpenCore + Monterey + Ventura + Sonoma support now! Only commercial (paid) support is available now to avoid spammy issues. No Mac system is required.
rumps - Ridiculously Uncomplicated macOS Python Statusbar apps
scrcpy - Display and control your Android device
bitbar - Put the output from any script or program into your macOS Menu Bar (the BitBar reboot)
macOS-KVM - Streamlined macOS QEMU KVM Hackintosh configuration using OpenCore and libvirt