migrating from yarn to pnpm

[imolorhe]

Fixes

Checks

• Replace lerna publish
• Remove nx (only kept since it is a transitive dependency of angular)
• Separate prepare (build) scripts from install script
• Use turbo for caching between script runs

Changes proposed in this pull request:

Summary by Sourcery

Migrate the project from Yarn to pnpm as the package manager, updating all scripts, configurations, and CI workflows accordingly. Add Docker-related documentation and configuration files to support containerized development and deployment.

Build:

• Switch from Yarn to pnpm as the package manager across the project, updating all relevant scripts and configurations.

CI:

• Update CI workflows to use pnpm instead of Yarn for installing dependencies and running build and test commands.

Documentation:

• Add a new README.Docker.md file with instructions for building, running, and deploying the application using Docker.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR migrates the project's package manager from Yarn to PNPM. The changes include updating the Dockerfile to use PNPM, modifying CI/CD workflows, updating package.json files, and adjusting build scripts across the monorepo to use PNPM commands instead of Yarn.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Migrated package manager from Yarn to PNPM	Added pnpm-workspace.yaml for monorepo configuration Updated package.json to use PNPM as package manager Modified workspace dependencies to use workspace:* protocol Removed Yarn-specific files (.yarnrc, yarn.lock) Added .npmrc configuration file	pnpm-workspace.yaml package.json .npmrc
Updated Dockerfile to use PNPM	Added multi-stage build process optimized for PNPM Added caching for PNPM store Updated base image to use Node 22.9.0 Improved build performance with better layer caching Added proper handling of production dependencies	Dockerfile compose.yaml
Modified CI/CD workflows for PNPM	Updated GitHub Actions workflows to use PNPM commands Modified caching strategies for PNPM dependencies Updated build and test scripts to use PNPM Adjusted deployment scripts to use PNPM commands	.github/workflows/_tests.yml .github/workflows/_publish-npm.yml .github/workflows/master.yml .github/workflows/firebase-hosting-merge.yml
Updated build and development scripts	Modified shell scripts to use PNPM commands Updated package build configurations Adjusted development environment setup scripts Updated test runner configurations	bin/dev.sh bin/deploy.js bin/publish_packages.sh packages/*/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

Visit the preview URL for this PR (updated for commit aee26b8):

https://altair-gql--pr2732-imolorhe-yarn-to-pnp-uc8jxbxz.web.app

_{(expires Sat, 21 Dec 2024 21:52:44 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 02d6323d75a99e532a38922862e269d63351a6cf}