Victor Gosse

Developer #css #javascript #reactJS #web #HTML

[Yoann Fleury 👨‍💻⚛️🦀 @YoannFleuryDev]

📣 Nouvel article sur mon blog
🕖 Je poste ce tweet tôt, comme ça si tu veux faire un peu de veille sur le trône, c'est fait pour toi 😉

https://t.co/29HP9YqKeD

[Remix 💿 @remix_run]

We have an announcement

https://t.co/WBG18EsLvG

[MUI org @MUI_hq]

Come see what we're cooking up next! 🎨🧑‍🍳

https://t.co/QTPzJeCMng

[Daniel Weinmann @danielweinmann]

Why React Router's new data APIs boost productivity

We've been using @remix_run at @seasonedcc for about two years now. And we consistently found that our teams are more productive with it.

In the past year or so, we also worked on a big React Router SPA to leverage the new data APIs. And the impact was very similar: a huge improvement in our team's throughput!

In this article, I'll share why React Router made that happen. There are many other benefits to adopting loaders and actions in your SPA, like page speed and better UX. But I'll focus on developer productivity today.

Before using the new data APIs, about two-thirds of our time was dedicated to managing our data fetching/mutation state. There are two main reasons for that:

1. When managing state at the component level, we need to check if the data was already fetched, render a pending UI if not, and render our component when the data is ready. A similar approach is necessary for dealing with errors. For every component.

2. Whenever we mutate data, we need to manually invalidate any state that became stale due to the changes. It's very hard to remember which states to invalidate at each mutation, and most of our bugs had to do with someone forgetting to revalidate something. And because we didn't know which component invalidated which state after each mutation, it took us a long time to diagnose these issues.

These challenges are not solved by TanStack Query (FKA React Query), SWR, and most similar libraries. But React Router 6.4+ makes them disappear!

Here's how we solved them with React Router:

1. When you use a loader, your component is only rendered after the data is fetched. So you don't have to worry about pending UI. In our app, we rely on a global pending UI for most interactions, and that's it. For dealing with errors, we rely on error elements and response-throwing to keep our component focused on the happy path.

2. React Router revalidates all loaders on the current route after each action, so we don't have to do any state management for mutations. Zero.

By eliminating these two problems, we reduced the cognitive load of our devs by an order of magnitude, I believe. Having to think so much about our app's state was slowing us down. And if you're not taking advantage of the data APIs yet, I bet it's dragging you down too!

https://t.co/77uWWlD5bu

[Addy Osmani @addyosmani]

Looking for examples of React Server Components & Next.js App Router?

📰 Hacker News: https://t.co/4O84xtNvld
🎥 Movies: https://t.co/MamHYREzF1
💰 Commerce: https://t.co/YBtUmR6nHr
🏠 AirBnB: https://t.co/h9deyu4NTw
📊 Taxonomy: https://t.co/nAeXt32BD1

My rough notes: https://t.co/pLOUfcscvj
and study the playground: https://t.co/8zQRQPCA3s

[Ilko Kacharov @kachar136]

Signs of a pro developer: Know when to stop by @BennettGarner https://t.co/XQjCisVWz0

[Thomas Dohmke @ashtom]

Today, we are announcing GitHub Copilot X: the AI-powered software development experience. We are not only adopting GPT-4, but introducing chat and voice for Copilot, Copilot in pull requests & much more. Read the details & watch the demos 👇

https://t.co/X8S8vl3gOA

[Matt Pocock @mattpocockuk]

Here's a quick thread on a super useful type helper you've probably never heard of (nope, not even advanced folks).

[Dominik 🔮 @TkDodo]

🤝React Query and React Router (the remixed one, v6.4) - how do they integrate? Should I use one or both for data fetching?

I went through the tutorial and integrated RQ into it. Read about it here: https://t.co/HChWqbYIa1

[Victor Gosse @VictorGosse]

@acemarke @TkDodo Love it ! Thanks

[Victor Gosse @VictorGosse]

@acemarke @TkDodo Hey, any advice on how to find those circular imports please ?

[Eddy Wilson @eddyw_dev]

💡TypeScript #3
🧙‍♂️Functional types - taking advantage of `this` and using intersections, we can mimic "interfaces as functions"

https://t.co/DRu6fvDDeV

[Matt Pocock @mattpocockuk]

🧵 The Ultimate TypeScript Thread 🧵

Here's everything I've learned from leading TS dev teams and working on XState's core team.

My goal is to turn you into a TypeScript wizard.

And yes, this thread is EVERGREEN - I'll add at least 3 more tips a week 🚀

Let's get started.

[React @reactjs]

React 18 is now available on npm!

Here’s an overview of what’s new in React 18, and what it means for the future.

https://t.co/6CAU1Fgznu

[GitHub @github]

You can now embed diagrams directly into your Markdown files, Issues and PR comments using Mermaid. Learn more - https://t.co/gfmNOp3HeJ

[Cory House @housecor]

8 ways to potentially speed up JavaScript project builds:

Build tools:
1. swc
2. esbuild

Fast, modern dev env:
3. Vite
4. Astro

Monorepo tools:
5. npm workspaces
6. Yarn workspaces
7. TurboRepo
8. Nx

Other good options I’m overlooking?

[Javan Makhmali @javan]

CSS tip: Use `font-variant-numeric: tabular-nums;` to align numbers neatly in a tables, progress counters, etc. Demo: https://t.co/Hnsz4OJIPg

[Dominik 🔮 @TkDodo]

@LydiaHendriks I have 😊
https://t.co/YtHlZUfHVA

[Cory House @housecor]

Yup is similar validation library. But Zod is unique because it throws an error when the data doesn't match the schema.

More on Zod vs Yup: https://t.co/yYhkLHEfGA