Skip to content

Conversation

@benmccann
Copy link
Member

@benmccann benmccann commented Oct 29, 2024

closes #13961

I tested this with the test project in that issue courtesy of our new pkg-pr-new setup and the tests passed

@changeset-bot
Copy link

changeset-bot bot commented Oct 29, 2024

🦋 Changeset detected

Latest commit: 29b0141

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@benmccann benmccann force-pushed the browser-node branch 3 times, most recently from e4431e0 to 47ae3ab Compare October 29, 2024 16:38
@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 29, 2024

pnpm add https://pkg.pr.new/svelte@14019

commit: 29b0141

@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 29, 2024

pnpm add https://pkg.pr.new/svelte@14019

commit: 2a666ad

@dominikg
Copy link
Member

wouldn't this prevent component testing wirh jsdom and a raf mock?

i don't understand why we use these conditions instead of a simple one-time check if requestAnimationFrame exists as a global at runtime initialization.

@benmccann
Copy link
Member Author

it wouldn't, but I was just about to close this with what I think is a simpler solution

@benmccann benmccann closed this Oct 29, 2024
@benmccann benmccann deleted the browser-node branch October 29, 2024 23:27
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.

SvelteSet does not behave correctly in Vitest

3 participants