verdaccio
yalc
Our great sponsors
| verdaccio | yalc | |
|---|---|---|
| 8 | 7 | |
| 15,818 | 5,365 | |
| 0.6% | - | |
| 9.8 | 1.1 | |
| 6 days ago | 3 months ago | |
| TypeScript | TypeScript | |
| 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.
verdaccio
-
📦 Everything you need to know: package managers
Verdaccio allows to setup a private proxy registry for Node.js
-
Npm link doesn't work with React Native, what do you use for testing local modules?
Verdaccio does okay for this
-
Monorepo or not?
I highly recommend using a package proxy like https://github.com/verdaccio/verdaccio instead of git submodules if you have more then one developer using your code/repo. Biggest factor is the cost of the developers time. Why teach them a different way to install dependancies when there is a standard way of doing things your CI/CD is simplified, the knowledge of git submodules is good to know, but this is now tribal knowledge on how to setup this up, update dependancies, etc...
-
Researcher hacks over 35 tech firms in novel supply chain attack
The goal of verdaccio is to make this less complicated. https://github.com/verdaccio/verdaccio
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.
-
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
What are some alternatives?
registry-sync - synchronize selected packages from a remote npm registry
AWS Lambda Router for NodeJS - AWS Lambda router for NodeJS
artifactory-pypi-scanner - Saves you from package injection!
Moleculer - :rocket: Progressive microservices framework for Node.js
Express - Fast, unopinionated, minimalist web framework for node.
dawson-cli - A serverless web framework for Node.js on AWS (CloudFormation, CloudFront, API Gateway, Lambda)
Hapi - The Simple, Secure Framework Developers Trust
Perk - A well documented set of tools for building node web applications.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
renovate - Universal dependency automation tool.
rubygems - Library packaging and distribution for Ruby.
pip - The Python package installer