Skip to content
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

test: update Cypress to v10 #1632

Merged
merged 2 commits into from Jul 14, 2022
Merged

Conversation

AriPerkkio
Copy link
Member

@netlify
Copy link

netlify bot commented Jul 12, 2022

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 11c68e8
🔍 Latest deploy log https://app.netlify.com/sites/vitest-dev/deploys/62cd1f23f6134a00085873d6
😎 Deploy Preview https://deploy-preview-1632--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@AriPerkkio
Copy link
Member Author

What's the correct way of updating the pnpm-lock.yaml while keeping the package.json version ranges in place?

"vite": "^2.9.12 || ^3.0.0-0",

Now I've just been running the pnpm i -D vite@beta in every single packages/* directory, and then reverting package.json changes. Also had to manually revert some vite: 3.0.0-beta.10 changes back to vite: 2.9.12 || ^3.0.0-0 in pnpm-lock.yaml. Is there a simpler way to do this?

@antfu antfu requested a review from JessicaSachs July 12, 2022 07:38
@antfu
Copy link
Member

antfu commented Jul 12, 2022

Thanks! I was just struggling to upgrade it.

What tool are you using to upgrade the deps?

@AriPerkkio
Copy link
Member Author

Just a simple pnpm install <package>@<version> from terminal. Then some manual work when reverting package.json changes. There is --lockfile-only flag, but even that one updates the package.json. 😕

@antfu antfu merged commit 6673389 into vitest-dev:main Jul 14, 2022
@AriPerkkio AriPerkkio deleted the test/cypress-10 branch July 14, 2022 16:29
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.

None yet

2 participants