Matan Borenkraout 🥬

Nooooo!!! 🥹🥹🥹

If your talk title has the word harnessing, that’s an AI generated title and we know it.

Remote Code Execution when accessing a malicious website while Vitest API server is listening ### Summary Arbitrary remote Code Execution when accessing a malicious website while Vitest API server is listening by Cross-site WebSocket hijacking (CSWSH) attacks. ### Details When [`api` o...

We've released patches for a critical security vulnerability. We strongly encourage projects to upgrade to versions 1.6.1, 2.1.9, or 3.0.5 as soon as possible.

I’ve published this here a while ago, unfortunately it probably got lost in the ocean of mentions and was unable to get someone to look at it…

bsky.app/profile/mata...

I had a Garmin watch before, I liked it but it was quite ugly and didn’t have AMOLED.. Mow the Garmin watches cost so much

I’m tired of my Apple Watch.. any recommendations for a smart watch that is both not too big and can provide useful training data?

Just as the bluesky handle

Bluesky just made me realize how many domains engineers have 😅

Hello everyone 👋

chore: upgrade RTL version to avoid peer-deps mismatch by MatanBobi · Pull Request #13738 · facebook/create-react-app Resolves #13721 This PR upgrades the installed version of RTL to resolve the peer deps issue. It also installs DTL because RTL version 16 requires DTL to be installed.

Test failures are reproducing on main too and are unrelated to my changes (I tried understanding what's happening there but I'm not too familiar with the codebase and want to unblock users)
github.com/facebook/cre...

Hi @ricky.fm, @danabra.mov, I know CRA is deprecated but since the release of React 19, it now breaks installation because RTL's version is expecting peer dep for React 18.
I've created this PR to update the RTL version according to our latest recommendations. Any chance to get your assistance?

Wdym? It doesn’t really learn based on your usage, just uses the open files as context.

Oh man why is my face all over this PR? 🤦‍♂️

feat: support async act by MatanBobi · Pull Request #10 · vitest-dev/vitest-browser-react Resolves #9 Still need to add a test for a suspended component, will work on it soon. Test added.

This is the test:
github.com/vitest-dev/v...

Thanks!

Or if I’m testing something that is entirely a react implementation detail that shouldn’t concern vitest-browser-react while using await act. And thanks for the reply, I appreciate it.

The behavior is inconsistent. If I simulate a promise that takes 1000ms to resolve it will show the fallback and if my promise takes 300ms it doesn’t show the fallback and just waits for the content to appear. My question is if there’s a threshold for showing the fallback on the client side

Code completions are highly affected from the open tabs, did you have something open? Or else it probably won’t know the styling.. Or is that something like writing a comment showing what you want to achieve and copilot not doing the work?

AFAIU, sync external store isn’t something they want to push, just a bandaid to not break the ecosystem.. Any mutation to a sync external store cannot be marked as non blocking and therefor don’t fit to the concurrent rendering model.

What do you call failure? What are you experiencing?

Is there any reference you can point me to?
Thanks!

Hi @ricky.fm, @danabra.mov!
I'm trying to migrate vitest-browser-react to use the new `await act` approach. I have a test where I try to assert a suspended component shows fallback and then the content when it's ready. I remember reading there's a threshold for showing fallback but couldn't find it.

Bummer, hope to see you next time!

@gil.tayar.org on stage in the JavaScript IL meetup!

Don't you just hate debugging a dropdown that hides once you focus out?!
Chrome DevTools to the rescue!

Just toggle the "Emulate a focused page" checkbox - and you're good to go 🔥

🎯🎯🎯
It says "Turn on all emails" 🤦‍♂️

Let's play a guessing game, you're seeing this blue button at the bottom of an unsubscribe page, what does it do?

I agree, though I believe that it also has an affect on the core package. This was just me giving a quick look, but you’re right.

19 is still bigger as you thought :)

Strongly agree here. Using default exports also make refactoring harder since people can rename the imported module whatever they want.

It does help :) thanks Artem