Skip to content

chore: use pnpm in isolated mode for frontend #451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

epipav
Copy link
Collaborator

@epipav epipav commented Jun 23, 2025

removes ./frontend from pnpm-workspace.yaml - instead we'll use it in isolated mode (by it's own pnpm-lock.yaml) until when/if we need shared libraries from the nuxt app

@epipav epipav requested review from Copilot and gaspergrom June 23, 2025 08:31
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Align pnpm configuration so the frontend app manages its own dependencies in isolated mode rather than via the monorepo workspace.

  • Remove frontend package entry from pnpm-workspace.yaml
  • Shift to using a standalone pnpm-lock.yaml in the frontend folder
Comments suppressed due to low confidence (1)

pnpm-workspace.yaml:6

  • [nitpick] Consider adding a comment in pnpm-workspace.yaml or updating the project README to explain why 'frontend' is managed in isolated mode instead of the shared workspace.
  - 'workers/temporal/*'

epipav added 2 commits June 23, 2025 10:39
Signed-off-by: anilb <epipav@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants