Thibaut Sabot

Lead developper at leboncoin

Buidling projects for 30M users with React & Next.js.

Helping our 60 Web developpers develop the #1 french website for classified advertisements.

About me

Hi there! I'm a 30 years old French developer currently living in Paris.

I'm a front end lead developer at Leboncoin.

I love talking about performance and I'm always eager to dig deeper into this field.

I find it essential to learn from others and share knowledge as much as I can!

My main missions are:

• Guaranteeing good practices (tests, syntax, algorithm complexity, design pattern)
• Assisting others on subjects where expertise is needed (debug, technical choices, ...)
• Advising and suggesting on the company's technical strategies
• Advocating for the technical choices of the Web developers
• Leading chapter meetings and workshops to make sure developers can learn from each others
• Constantly checking the health of our technical stack (Performance, usage of our design system, metrics, migrations, ...)

In my spare time I like to contribute to Next.js by answering discussions or creating pull requests.

My recent blog posts

Built my website without compromise using to Next.js

How we are improving our Web performance at Leboncoin

How we migrated our legacy frontend to NextJS

My recent activity

✕─◻

Discussions

12

[next.js] - Hello ! I don't think you need both .eslintrc.json and .eslinrc.js. In fact it might be the root cause of your issue. The second file seems to override the first. If you get rid of .eslintrc.json to only keep .eslinrc.js and add the next plugin at the end like : "env": { "browser": true, "es2021": true }, "extends": [ "eslint:recommended", "plugin:react/recommended", "next/core-web-vitals" ], ... it should fix your problem.

3

[next.js] - Hello ! If I understand correctly, the ready - started server on message is triggered after the webpack build is finished. What do you think about watching the end of the webpack build instead of the Next server start ? It might not be exactly what you want but it should be pretty close to. In your next.config.js file you could use an afterEmit or a done hook (inside the Webpack config section). If you don't want to do it by hand, you could also use a Webpack plugin such as webpack-shell-plugin. onBuildEnd or onBuildExit should do the trick. Hope it helps !

3

[next.js] - Hello. Can you share your eslint config ? If you extends "next" (like the docs suggest : https://nextjs.org/docs/basic-features/eslint) you won't get the first error as it is disabled. See : https://github.com/vercel/next.js/blob/canary/packages/eslint-config-next/index.js#L19 Also react/jsx-props-no-spreading is not even in the recommended config. You probably have it included in your custom configuration.

1

[next.js] - Hello ! It looks like your are using the active-class-name example. A patch has been merged here #28481 prop-types has been removed from Next internal package.json since this PR #27196, because it's not needed anymore for internal files. If you want to use it on your own you probably need to install it yourself.

✕─◻

Commits