lerna VS pnpm

On Netlify's enterprise tier, approximately 46% of builds are monorepos, with the majority leveraging Nx and Lerna. Recognizing this trend, Netlify has focused on enhancing the setup and deployment experiences for monorepo projects. In particular they worked on an "automatic monorepo detection" feature. When you connect your project to GitHub, Netlify automatically detects if it's part of a monorepo, reads the relevant settings, and pre-configures your project. This eliminates the need for manual setup. This feature also extends to local development via the Netlify CLI.

This is the exact problem monorepos were born to solve. Not only will a monorepo let you share UI components, you'll be able to gradually add shared application logic as well (for instance, do all of your apps have their own logic for connecting to a database? you could roll that into a shared library with a monorepo). There are a lot of tools for accomplishing this in JS, but probably the most popular is lerna, which is built on top of NX (though lots of teams roll their own monorepo in nx without lerna, which IMO is a totally valid option).

To begin, you need to prepare your environment. A few ways to build a React package include tools like Bit, Storybook, Lerna, and TSDX. However, for this tutorial, you will use a zero-configuration bundler for tiny modules called Microbundle.

If so, are you using a monorepo tool like Nx or Lerna? If not, start there and see if it solves your problem.

I mean I don't know what your monorepo looks like, but for example infernojs (actually written with typescript) uses lerna, and lerna seems simpler than typescript references

Tools for publishing, such as Lerna (when using the --conventional-commit flag), follow this convention when incrementing package versions and generating changelog files.

We could improve part of this by using something like Lerna. With the right configuration, Lerna can be really helpful.

It feels dirty to be adding express as a dependency to a react project, but I'm pretty sure TRPC requires all of client and server code to be in the same node.js project, since types are shared. I've read that you can use a tool like Lerna to share types between node projects, but it requires a build step, which would diminish the benefits of TRPC.

For more information, check out the PR

FROM node:18.16.0-alpine RUN apk add \ curl \ git \ && rm -rf /var/cache/* \ && mkdir /var/cache/apk RUN mkdir -p /app WORKDIR /app RUN mkdir -p /bin && curl -fsSL "https://github.com/pnpm/pnpm/releases/download/v8.6.3/pnpm-linuxstatic-x64" -o /bin/pnpm; chmod +x /bin/pnpm; ENV PATH /app/node_modules/.bin:$PATH ADD package.json pnpm-lock.yaml .npmrc /app/ RUN pnpm install ADD . /app RUN pnpm run build EXPOSE 5000 CMD [ "pnpm", "start" ]

The conflict resolution algorithm for pnpm is maintained by the @pnpm/merge-lockfile-changes project.

What version of pnpm are you using? I found this issue, maybe it's related?

Please check here https://github.com/nrwl/nx-labs/issues/34 and here https://github.com/pnpm/pnpm/issues/1501

I had been using https://github.com/pnpm/pnpm for some web projects and it's really fast due it caches all dependencies so different projects use the same cached dependency, this results in really fast build times.

If using pnpm, you can create a dedicated lockfile for a sub-directory using https://github.com/pnpm/pnpm/tree/main/packages/make-dedicated-lockfile. This means shared org1 org2 could have their own lockfiles, preventing any differences in shared when used in each different monorepo workspace.

## Patch Changes * Don't write the `pnpm-lock.yaml` file if it has no changes and `pnpm install --frozen-lockfile` was executed [#6158](https://github.com/pnpm/pnpm/issues/6158). * Fix git-hosted dependencies referenced via `git+ssh` that use semver selectors [#6239](https://github.com/pnpm/pnpm/pull/6239). * When publish some package throws an error, the exit code should be non-zero [#5528](https://github.com/pnpm/pnpm/issues/5528). * Only three paths are displayed in `pnpm audit` output [#6203](https://github.com/pnpm/pnpm/issues/6203) * Aliased packages should be used to resolve peer dependencies too [#4301](https://github.com/pnpm/pnpm/issues/4301).

I prefer use pnpm but you can use npm, yarn, ...etc.

pnpm