yalc
rumps
yalc | rumps | |
---|---|---|
7 | 5 | |
5,400 | 3,039 | |
- | - | |
1.1 | 2.4 | |
4 months ago | about 1 month ago | |
TypeScript | Python | |
MIT License | BSD 3-clause "New" or "Revised" 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
rumps
-
reKarma - my first public app ever. MacOS menu bar app that checks reddit's karma of given user.
Not seen rumps before.
- What are the not-so-obvious tools that you don't want to miss?
-
For the Macbook Pro, how would you create a script in which an alarm goes off when the power cord is disconnected?
I've got a Mac OS status bar app written in Python here that could easily be modified to do this. It uses rumps to create the status bar app and psutil to monitor the plugged/unplugged state and charge status. I use it to remind me to plug in the charger when charge gets below a certain level and unplug the charger when charge gets above a certain level. Here's how to get the plugged in status (which you could check periodically on a loop)
-
Costum menu bar app with python & rumps
By chance a got to know rumps. A really fantastic python package for making menu bar apps on MacOS. With this it's really easy to build a small menu bar app that suits ones personal needs.
-
Create a menubar app for macOS, just using Python
Rumps on Github py2app documentation Icon by Freepik
What are some alternatives?
verdaccio - 📦🔐 A lightweight Node.js private proxy registry
MacOS-Menu-Bar-Picker - Costum menu bar entry for MacOS - build with rumps and py2app.
renovate - Universal dependency automation tool.
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
Musicbar
breakpad - Mirror of Google Breakpad project
py-applescript - An easy-to-use Python wrapper for NSAppleScript, allowing Python scripts to communicate with AppleScripts and AppleScriptable applications.
bitbar - Put the output from any script or program into your macOS Menu Bar (the BitBar reboot)
osascript.py - :apple: :snake: osascript (AppleScript) python implementation