|7 months ago||2 days ago|
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.
Unable to resolve module react-redux
1 project | reddit.com/r/reactnative | 20 Jan 2022
Take a look at yarn workspaces or lerna
How we reduced our nodejs monorepo build time by 70%
4 projects | dev.to | 10 Jan 2022
We migrated from yarn workspaces & lerna to PNPM and nx.dev
Using API request between Next FE and Express BE
2 projects | reddit.com/r/reactjs | 6 Jan 2022
If you want them within the same repo, I don't know if I'd put it directly in the Next.js app, but you could use a tool like Nrwl NX or Lerna to handle both apps in a monorepo.
Monorepos and Workspaces - an introduction
8 projects | dev.to | 3 Jan 2022
tldr; When making a monorepo, it generally consist of workspaces (can use npm, yarnor pnpm), but additional tooling exists like lerna and turborepo (and lots of others too) to help with easing the problems of managing lots of interlinked packages
My FrontEnd Stack
6 projects | dev.to | 2 Jan 2022
Lerna : https://github.com/lerna/lerna Yarn : https://yarnpkg.com/
Aggregating Unit Test Coverage for All Monorepo’s Packages
3 projects | dev.to | 31 Dec 2021
It is a good time to mention that my Pedalboard monorepo uses the Jest testing framework. The first step is to add a script at the root project level, with which I can run my test coverage for all the nested packages. Should be straightforward, using Lerna for that. Here is how my scripts look like now:
A complete AWS Architecture for Module-federated micro-frontends
1 project | dev.to | 24 Dec 2021
My next series of articles presents a complete server-less architecture aiming at deploying and hosting client-side mono-repo micro-frontends on AWS, based on Webpack Module Federation plugin and Lerna.
Looking for a way to share and sync a directory across projects.
Lerna, but my biggest issues here are that this seems like a total over-kill and would add a ton of complexity for a simple problem, and not to mention time invested to learn how to use it.
I'm working on multiple projects simultaneously and I reuse a lot of my JS functions and use Webpack to bundle them. When I update/add a function to the file in one project, I have to do them in the other projects as well to use the function. Is there any way I can improve this?
You can either create your own structure use something like lerna. There are other monorepo tools as well, like e.g. nx, but let's focus on lerna.
9 projects | dev.to | 20 Dec 2021
As always, there is still some room for improvement. For example, you might want to use Lerna's package hoisting to reduce the size of the node_modules.
What are some alternatives?
nx - Smart, Fast and Extensible Build System
pnpm - Fast, disk space efficient package manager -- 快速的，节省磁盘空间的包管理工具
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
husky - Git hooks made easy 🐶 woof!
rushstack - Monorepo for tools developed by the Rush Stack community
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
ultra-runner - 🏃⛰ Ultra fast monorepo script runner and build tool
Microbundle - 📦 Zero-configuration bundler for tiny modules.
berry - 📦🐈 Active development trunk for Yarn ⚒
single-spa - The router for easy microfrontends
react-native-web - React Native Components and APIs for the Web