Skip to content

chore: fix pnpm-workspace.yaml file - #99

Merged
andersonresende merged 4 commits into
mainfrom
chore/fix-ci-next-js
Dec 17, 2025
Merged

andersonresende merged 4 commits into
mainfrom
chore/fix-ci-next-js

Conversation

@raisiqueira

@raisiqueira raisiqueira commented Dec 17, 2025 •

Copy link
Copy Markdown
Contributor

Description

  • Fix the pnpm-workspace.yaml file that was causing CI issues

Motivation and Context

Screenshots (if appropriate):

Steps to reproduce (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires documentation updates.
  • I have updated the documentation accordingly.
  • My change requires dependencies updates.
  • I have updated the dependencies accordingly.

Summary by Sourcery

Build:

  • Configure pnpm workspace to include the Next.js frontend project as a package for proper workspace resolution.

Signed-off-by: Rai Siqueira <rai93siqueira@gmail.com>
@raisiqueira raisiqueira self-assigned this Dec 17, 2025
@raisiqueira raisiqueira added the enhancement New feature or request label Dec 17, 2025
@sourcery-ai

sourcery-ai Bot commented Dec 17, 2025 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a proper pnpm workspace definition to the Next.js frontend so CI can correctly resolve the local package, while preserving the existing onlyBuiltDependencies configuration for sharp.

Flow diagram for pnpm workspace resolution during CI

flowchart TD
  A[Start CI job] --> B[Run pnpm install]
  B --> C[Read pnpm-workspace.yaml]
  C --> D{packages defined?}
  D -->|No before change| E[Workspace root not recognized]
  E --> F[Local Nextjs package resolution fails]
  F --> G[CI issues with dependencies]

  D -->|Yes after change| H[packages: .]
  H --> I[Workspace root recognized]
  I --> J[Resolve local Nextjs frontend package]
  J --> K[Read onlyBuiltDependencies: sharp]
  K --> L[Build sharp during install]
  L --> M[Dependencies resolved successfully]
  M --> N[CI job continues]
Loading

File-Level Changes

Change Details Files
Define the Next.js frontend directory as a pnpm workspace package to fix CI resolution issues.
  • Introduce a top-level packages section in the pnpm workspace configuration
  • Register the current directory as the only workspace package using the '.' glob
  • Keep the existing onlyBuiltDependencies configuration for sharp unchanged
nextjs-frontend/pnpm-workspace.yaml

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. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Signed-off-by: Rai Siqueira <rai93siqueira@gmail.com>
Signed-off-by: Rai Siqueira <rai93siqueira@gmail.com>
@andersonresende
andersonresende merged commit 62b6745 into main Dec 17, 2025
13 checks passed
@andersonresende
andersonresende deleted the chore/fix-ci-next-js branch December 17, 2025 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants