Mono-Repository Guidance and Tooling - Githubissues

nodeshift / nodejs-reference-architecture

The Red Hat and IBM Node.js Reference architecture. The teams 'opinion' on what components our customers and internal teams should use when building Node.js applications and guidance for how to be successful in production with those components.

https://nodeshift.dev/nodejs-reference-architecture/

Apache License 2.0

1.66k stars 120 forks source link

Mono-Repository Guidance and Tooling #92

Closed roastlechon closed 2 years ago

bennypowers commented 2 years ago

Following up with a call I had with @mhdawson, I put together this short review of how PFE aligns and differs from these recommendations

How does PFE align with monorepo tooling recommendations

Legend

✅ PFE aligns with recommendations
⚠️ PFE differs mildly or from optional recommendations
❌ PFE differs strongly from recommendation

Workspaces

✅ PFE uses NPM workspaces, along with lerna. PFE only uses lerna for lerna run --parallel, it does not use lerna for installing or managing packages.

Building

✅ PFE uses npm scripts as well as custom build scripts based on tsc and esbuild. PFE vends those build scripts as well.
⚠️ PFE does not use bazel.
✅ PFE uses conventional commits and validates them in CI.

Publishing

✅ PFE uses changesets for publishing

Package Releasing

✅ PFE follows semver (via changeset)

roastlechon commented 2 years ago

Addresses #64

mhdawson commented 2 years ago

We discussed in the Ref Arch meeting this week and agreed it was ready to land