yalc
entr
yalc | entr | |
---|---|---|
7 | 47 | |
5,419 | 4,062 | |
- | - | |
1.1 | 6.8 | |
4 months ago | about 2 months 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
entr
- Entr – tool for watching files and running commands
-
Meet entr, the standalone file watcher
entr ("Event Notify Test Runner"; GitHub), is a command-line tool written by Eric Radman that allows running arbitrary commands whenever files change.
-
How to build a website without frameworks and tons of libraries
I use something very similar on https://lunar.fyi and https://lowtechguys.com but I wouldn’t call this “simple” anymore.
They use Jinja templating, I prefer Slim (https://github.com/slim-template/slim#syntax-example) which has a more Pythonic syntax (there is plim [0] in Python for that)
I use Tailwind as well for terse styling and fast experimentation (allows me to write a darkMode-aware and responsive 100 line CSS in a single line with about 10 classes)
For interaction I can write CoffeeScript directly in the page [1] and have it compiled by plim.
I run a Caddy static server [2] and use Syncthing [3] to have every file save deployed instantly to my Hetzner server.
I use entr [4] and livereloadx [5] to rebuild the pages and do hot reload on file save. All the commands are managed in a simple Makefile [6]
———
You can already see how the footnotes take up a large chunk of this comment, this is not my idea of simple. Sure, the end result is readable static HTML and I never have to fight obscure React errors, but it’s a high effort setup for starters.
Simple for me would be: write markdown files for pages, a simple CSS for general styling (should be optional), click to deploy on my domain. Images should automatically be resized to multiple sizes and optimized, videos re-encoded for smaller filesize etc.
I have mostly implemented that for myself (https://notes.alinpanaitiu.com/How%20I%20write%20this%20blog...) but it feels fragile. I’d rather pay for a professional solution.
[0] https://plim.readthedocs.io/en/latest/
[1] https://github.com/FuzzyIdeas/lowtechguys/blob/main/src/rcmd...
[2] https://caddyserver.com/docs/command-line#caddy-file-server
[3] https://syncthing.net
[4] https://github.com/eradman/entr
[5] https://nitoyon.github.io/livereloadx/
[6] https://github.com/FuzzyIdeas/lowtechguys/blob/main/Makefile
- How to start a Go project in 2023
-
[Guide] A Tour Through the Python Framework Galaxy: Discovering the Stars
Try entr for fast reloading. Another one is hupper.
- Use entr when working on you rice for auto config refreshing
- The Unix process API is unreliable and unsafe
- How do you develop cloud-native applications locally on Kubernetes?
-
What are the not-so-obvious tools that you don't want to miss?
entr
- Test driven development is adhd dream
What are some alternatives?
verdaccio - 📦🔐 A lightweight Node.js private proxy registry
watchexec - Executes commands in response to file modifications
renovate - Universal dependency automation tool.
nextjs-tailwind-ionic-capacitor-starter - A starting point for building an iOS, Android, and Progressive Web App with Tailwind CSS, React w/ Next.js, Ionic Framework, and Capacitor
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
modd - A flexible developer tool that runs processes and responds to filesystem changes
breakpad - Mirror of Google Breakpad project
swc-node - Faster ts-node without typecheck
rumps - Ridiculously Uncomplicated macOS Python Statusbar apps
air - ☁️ Live reload for Go apps
bitbar - Put the output from any script or program into your macOS Menu Bar (the BitBar reboot)
vim-test - Run your tests at the speed of thought