fix(browser): allow for pretty-format as a sibling dependency

[nicojs]

Description

Solves #4570 by adding a missing dependency of @vitest/snapshot to the dependency optimization.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 canceled.

Name	Link
🔨 Latest commit	8ac8628
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/65623bde10faaa00084079a9

[nicojs]

• I've got the feeling 'vitest > pretty-format', can be removed from dependency optimization since vitest doesn't depend on pretty-format (anymore?). Let me know if this is correct, and I'll remove it.
• Do you want me to add a test for this? If so, please point me in the right direction. For example, can I add pretty-format as a dependency to "test/browser"?

[AriPerkkio]

Tested this manually by patching node_modules using the linked minimal reproduction.

It also looks like this issue doesn't come up with pnpm. The vitest-tests repository has a browser setup with pnpm only: https://github.com/vitest-tests/browser-simple. As Vitest's main repository (this project) is using pnpm it's difficult to create failing test cases here. Maybe we'll need vitest-tests/browser-simple-npm.

[ghiscoding]

Tested this manually by patching node_modules using the linked minimal reproduction.

It also looks like this issue doesn't come up with pnpm. The vitest-tests repository has a browser setup with pnpm only: https://github.com/vitest-tests/browser-simple. As Vitest's main repository (this project) is using pnpm it's difficult to create failing test cases here. Maybe we'll need vitest-tests/browser-simple-npm.

I have no idea if that would work or not, but have you ever thought of maybe using corepack for some tests or a workflow? I never personally use corepack myself, but I was wondering if it could help here or not? Maybe this GitHub Action setup-node issue 531 is related to what I just said which I think is not yet possible but they have a promising PR to support it but it seems extremely long to merge the PR

[patrickberkeley]

@sheremet-va sorry to bother you, but any chance you could cut another beta release for this fix?