Refresh challenge

[oliviertassinari]

We could:

• Upgrade React to v18 Refresh dependencies #4
• Upgrade React to v19, etc.

tech-challenge-full-stack/package.json

Line 21 in 855e033

"react": "^18.2.0",

• Update Next.js to the pages directory

tech-challenge-full-stack/pages/_document.tsx

Line 7 in d7024ec

export default class MyDocument extends Document {

• Move from yarn to pnpm

[Janpot]

Honestly, I'm not sure we should push candidates even deeper into Next.js's paradigms. It's so opinionated and aimed at the static website use-case. It has these strong constraints on routing, it doesn't support API routes, it's all vendor specific and non-standardized. I'd like to gauge candidates capability to understand the basics of React, and the basic anatomy of web servers. If anything, I think for the future of this challenge we could rather aim towards getting rid of Next.js and offer something more bare bones.

Opening #4 already for the dependencies.

[oliviertassinari]

On

this is something that has already surfaced in the past with @samuelsycamore, @danilo-leal, and @mj12albert. I think there is already a general consensus on this, I had the same pain. I have added the point to the TODO list in mui/material-ui#34905 (in cases there is no existing issues about it already)

[oliviertassinari]

Honestly, I'm not sure we should push candidates even deeper into Next.js's paradigms. It's so opinionated and aimed at the static website use-case. It has these strong constraints on routing, it doesn't support API routes, it's all vendor specific and non-standardized. I'd like to gauge candidates capability to understand the basics of React, and the basic anatomy of web servers. If anything, I think for the future of this challenge we could rather aim towards getting rid of Next.js and offer something more bare bones.

@Janpot Should we go down the Vite + express API route then?

[Janpot]

🙂 I typed that comment because I got frustrated with the example. I removed it again after I started playing around with app dir and this challenge and it didn't feel like a good fit. But fair enough, should have signaled this 👍

Should we go down the Vite + express API route then?

I think that would be a good stack for the challenge. The only thing that holds me back from it is vitejs/vite#12423. It would be a pity doing a coding challenge and then have this bug eat all your time.