feat: prepare for pnpm 8 #3331
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Blocks
#3317 chore(deps): update pnpm to v8
vikunja/frontend
Reference: vikunja/frontend#3331
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "dpschen/frontend:feature/prepare-pnpm8"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
By commiting the new lockfile format before using pnpm 8 we can improve the migration process.
Related: #3317
Note: the new lockfile format and the settings here should all already be compatible with pnpm 7.
Hi dpschen!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://3331-feature-prepare-pnpm8--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
feat: prepare for pnpm 8to wip: feat: prepare for pnpm 8pnpm told me
That's probably due to the old pnpm I use. Can you rebase on main which has the updated nix flake with the newer pnpm?
Since which version is the new lockfile format supported?
cb8cbc22dd
toeb8972ee50
eb8972ee50
to3f53d6d35c
wip: feat: prepare for pnpm 8to feat: prepare for pnpm 8Doing now!
Seems like since version v7.24.0, see: https://pnpm.io/7.x/npmrc#use-lockfile-v6
That seems to have worked.
Ok, so this can be merged?
Let me update renovate first.
Just to be clear: the changes in this branch should be compatible with the last few versions of pnpm@7
Yes, but it's been a long while since I last updated renovate and we need to do it anyway for pnpm 8.
It is updated now, merging...