Yannick Croissant (@[email protected])

Passionate Front End Developer, JavaScript Enthusiast and PC Gamer. Tech Lead at @CANALTechTeam

Also on Mastodon: @[email protected]

[Paris TypeScript @ParisTypeScript]

Hello les TypeScripters 👋

Nouveau meetup en approche et non des moindres, le 40éme 🎉

Rendez-vous le 12 novembre chez @avec_alan !

Le programme arrive d'ici peu 😉

https://t.co/tV0tnqOpKi

[Jordan Harband @ljharb]

v7.35.0 of https://t.co/lA0snKeL3A has just been released, with eslint 9 and flat config support.

Please try it out, and file issues if you have any trouble!

[Daniel Rosenwasser @drosenwasser]

Here's a fun little perf win I managed over the weekend on eslint-plugin-react: https://t.co/2oFinIwVgY

This shaves off about 1/3 of the time spent linting TypeScript/JavaScript in the @getsentry repo - about 70 seconds!

[terminally onλine εngineer @tekbog]

instead of leetcode we need 5 rounds of interviews to see if you can understand the legacy service that's failing on a decomisioned cloud api with no documentation and you have to find the engineer who first wrote part of the code so he can point you to a 5 years old jira ticket

[Eunjae Lee @eunjae_lee]

I'm giving a lightning talk at this event on this Wednesday !

<Writing Your First Vite Plugin>

[Josh Goldberg 🦋 @JoshuaKGoldberg]

@tseslint @geteslint ✨ Announcing typescript-eslint v8 Beta ✨

https://t.co/GJbOjz8jZt

[React @reactjs]

React Conf 2024 recap!

https://t.co/7LE0bXzLDX

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

💡 TIL about Compute Pressure API

This permits observing compute pressure on things such as:
- CPU
- GPU
- thermals

Pressure levels: critical > serious > fair > nominal

This just landed in Chrome 125

This could be useful under the hood for Concurrent React? 🤔

[Artem Sapegin @iamsapegin]

New post on my blog: Modern React testing, part 5: Playwright

https://t.co/nEGsoumo1h

@playwrightweb

[Node.js @nodejs]

Node.js 22 is here 😎

Featuring: require()ing ESM graphs, WebSocket client, updates of the V8 JavaScript engine, and more.

Big thank you to @_rafaelgss and @satanacchio for their work on this 🎉

[🖖 Sylvain PONTOREAU @spontoreau]

Say hello to the new React Paris meetup !

https://t.co/q8grAXSqhz

Gabriel and I are looking for a host and speakers for the first one ! Feel free to reach me if you are interested 😉

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

React 19 will improve DX!

Notably hydration errors + reporting 🎉

Error handling was refactored + 2 new React APIs 🧪️
💡 onRecoverableError: now includes Error.cause with a helpful message
🆕 onCaughtError: catch boundary errors
🆕 onUncaughtError: catch other errors

[ESLint @geteslint]

This release also includes the new config inspector written by the prolific @antfu7:

https://t.co/AFfyebYl6X

[ESLint @geteslint]

ESLint v9.0.0 has been released! 🎉

https://t.co/DHolK9xqyn

[Matt Pocock @mattpocockuk]

OH MY GOD IT'S HAPPENING

In TS 5.5, type predicates will be inferred automatically from functions that return a narrowing statement.

No more 'val is string' to force TypeScript's hand.

@danvdk, I can't believe you got it merged. Incredible work.

[Mateusz Burzyński @AndaristRake]

Oh, yeeeeah, this has been merged 😍😍😍😍😍😍😍😍😍

TS 5.5 is gonna be one of the most epic releases in a while, once again - huge props to @danvdk

https://t.co/GyiyTAWSM7

[TypeScript @typescript]

Announcing TypeScript 5.4! 📢

Now with:

✅ Smarter control-flow analysis in closures
✅ The `NoInfer` utility type
✅ Broader support for bundlers and runtimes
✅ Quick fixes for missing parameters
✅ Improved auto-imports

and more! Try it today!

https://t.co/qqSG1bCGGL

[Deno @deno_land]

JSR - the JavaScript Registry - is now available in public beta.

🛠️ TypeScript first, ESM only
🌐 Works across runtimes (Node, Deno, Bun, workerd and more) and alongside npm/yarn/pnpm
🤗 Free and open source

Read about it on the Deno blog: https://t.co/oDxDyGsOtf

[Dan Vanderkam 🦋 @danvdk]

Put up my second #TypeScript PR! It allows the type checker to infer "type predicates" when a function returns a boolean that's tied to a refinement on one of its parameters. I have no idea if it'll be accepted, but I sure learned a lot implementing it!
https://t.co/AX5Y9nH1aw

[Andrew Clark @acdlite]

By the end of 2024, you’ll likely never need these APIs again:

• useMemo, useCallback, memo → React Compiler
• forwardRef → ref is a prop
• React.lazy → RSC, promise-as-child
• useContext → use(Context)
• throw promise → use(promise)
• <Context.Provider> → <Context>