feat: possible fix for pnpm ci errors #2413
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.
Dependencies
No dependencies set.
Reference: vikunja/frontend#2413
Loading…
Reference in New Issue
No description provided.
Delete Branch "dpschen/frontend:feature/possible-pnpn-fix"
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?
WIP: feat: possible fix for pnpm ci errorsto feat: possible fix for pnpm ci errors@ -47,3 +47,3 @@
CYPRESS_CACHE_FOLDER: .cache/cypress
commands:
- corepack enable && corepack prepare pnpm@7.9.3 --activate && pnpm config set store-dir .cache/pnpm
- corepack enable && corepack prepare pnpm@7.12.2 --activate && pnpm config set store-dir .cache/pnpm
Do we need to change this every time a new pnpm version is released?
The corepack prepare might not be necessary after all: https://pnpm.io/installation#using-corepack
I removed it. Let's see if that works.
If I understand it correctly it should then use the version defined in
package.json
.Seems to work.
Hi dpschen!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://2413-feature-possible-pnpn-fix--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!
b926d8670b
toa199fc7a8e
I think you need to sign this again, since I had to rebase to include the http => https change.