masimou

Software engineer by choice

[masimou @masimou2]

Do we still need React Query with Next.js v14? https://t.co/Kl5AgGUyDJ

[masimou @masimou2]

I am not gonna lie. Next.js is getting better and better, but unfortunately it has a steep learning curve. Now its clear to me what I get with v13

[masimou @masimou2]

Personally, I tend to use a combination of private folders, organizing files per feature

[masimou @masimou2]

What's your preferred project structure with next.js and server components?

[masimou @masimou2]

Hey @mattpocockuk. I don't remember when, but a few months ago you shared a TS utility that prettify the strcuture of a type. Can you share it again?

[masimou @masimou2]

I had to update the dependencies on 4 backend services written in go. It took me a total of 4 hours to upgrade them. On the other hand, I am still battling to update my react project. I love the stability of the go ecosystem

[masimou @masimou2]

If you are trying to improve the performance of your website, web vitals can be a great indicator of those pain points. I wrote an article that explains how those metrics behave. Check it out! https://t.co/vemENWX3AZ

[masimou @masimou2]

If you are trying to improve the performance of your website, web vitals can be a great indicator of those pain points. I wrote an article that explains how those metrics behave. Check it out! https://t.co/vemENWX3AZ

[masimou @masimou2]

I really like the approach next.js follows in terms of how to render. ISG by default and use flags to switch to either SSR or SSG

[masimou @masimou2]

@mattpocockuk In addition to what you said, I feel that a returned type should be used only if you have multiple branches in a condition and you want to lock it on a single type. In any other case, it's likely something wrong with the structure of my code or I need to use function overloading

[masimou @masimou2]

Optimizing build times in a create-react-app project. Check out here: https://t.co/6qKnJUcZsh

[masimou @masimou2]

Optimizing build times in a create-react-app project. Check out here: https://t.co/6qKnJUcZsh

[masimou @masimou2]

@leopradel I have also noticed that the bundle size a slightly larger, but nothing really concerning

[masimou @masimou2]

@leopradel I did a similar benchmark as what you describe in your personal blog. I replaced babel-loader in react-scripts with esbuild. Here are my findings:
default build time in react-scripts: 3m 50.88s
esbuild build time: 58.67s

[masimou @masimou2]

@leopradel Yea, unfortunately that's a legacy codebase and I don't think it's the right time for a big refactoring. However, at some point we should move to https://t.co/KJ5YRVyHS5 and get all those out of the box optimizations.

[masimou @masimou2]

Planning to benchmark swc as well, but I need to upgrade our codebase to be compatible with react-scripts@v5

[masimou @masimou2]

@flaviocopes https://t.co/6u5WQrzE5l or https://t.co/DrM4YatVoi

[masimou @masimou2]

Just released an npm package that allows to run a GraphQL server from a solid-start API route. Hope you like it: https://t.co/G7bXZyT5ZK

[masimou @masimou2]

Unsurprisingly, I ended up with hydration problems in next.js v13 after only 2 hours playing around with it. Let me see what I can learn...