Skip to content

chore: update pnpm settings #51

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.

Sign up for GitHub

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

Merged
witoszekdev merged 1 commit into from
Jan 23, 2026
Merged

chore: update pnpm settings #51

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"version": "0.1.0",
"type": "module",
"private": true,
"packageManager": "pnpm@9.12.3",
"packageManager": "pnpm@10.28.1",
"scripts": {
"build": "next build",
"check-types": "tsc --noEmit",
Expand Down
3 changes: 3 additions & 0 deletions pnpm-workspace.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
blockExoticSubdeps: true
minimumReleaseAge: 1440 # 24h
trustPolicy: no-downgrade
Comment on lines +1 to +3
Copy link

Copilot AI Jan 21, 2026

Choose a reason for hiding this comment

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

The pnpm-workspace.yaml file is missing the required 'packages' field that defines which directories are part of the workspace. If this is intended to be a single-package repository with no workspace packages, the typical configuration would be 'packages: ["."]' or you may not need a pnpm-workspace.yaml file at all. If workspace functionality is needed, please add a packages field. Otherwise, consider whether this file is necessary.

Copilot uses AI. Check for mistakes.