website Update react to v19, update eslint, replace chroma-js with colord and replace outdated deps

Upgrade react and its dependencies to version 19.
Update eslint configuration.
Replace react-scripts with vite.
Replace react-router-cache-route with keepalive-for-react. react-router-cache-route does not work with react-router v6+.
Replace use-query-params with nuqs. use-query-params does not work with new react.
Replace chroma-js with colord. It weighs 5 times less (bundle size reduced from 390kb to 352kb) and has built-in typing.

Apr 09 '25 20:04 nakrovati

How do you deploy this project @SuspiciousLookingOwl ?

Apr 20 '25 07:04 waghanza

Could you make some preview (screenshots in this PR) @nakrovati ?

Jun 29 '25 09:06 waghanza

Hi, here are some screenshots. They don't really make sense as the UI is 1 to 1 what it was.

Jun 29 '25 22:06 nakrovati

I haven't worked with netlify, but it seems like repo owner just need to change the build directory from output to dist and deploy with netlify CLI (if you don't have CI/CD configured).

Jun 30 '25 09:06 nakrovati

If you want to rework on this, I mean trigger a deployment when master is updated, feel free.

Jul 01 '25 05:07 waghanza

In general, a netlify account holder can just connect repo through netlify and not have to write triggers and github worlflows, as the guide says https://docs.netlify.com/get-started/.

This is the easiest and fastest way, I deploy sites to vercel the same way.

Jul 01 '25 13:07 nakrovati

If you want to switch and setup a vercel account for this, be my guest

@SuspiciousLookingOwl has no time to maintain it, I suppose 😛

Jul 10 '25 13:07 waghanza

Ok, then write the email to which you want to create the account, or if you want to register it to your email, I will give you instructions how to deploy it, it's a matter of a few minutes. In the meantime you can check it deployed from my account - https://website-ten-beryl-94.vercel.app.

Jul 11 '25 16:07 nakrovati

Hi @waghanza, so what did you decide about Vercel?

Jul 21 '25 13:07 nakrovati

@nakrovati your proposal is still somewhere in my memory 😛

I've published https://the-benchmarker.netlify.app and will take some times later to automatize

btw, thanks for you work

Oct 22 '25 12:10 waghanza

@nakrovati your proposal is still somewhere in my memory 😛

I've published https://the-benchmarker.netlify.app and will take some times later to automatize

btw, thanks for you work

I suggested Vercel because it was 2–3 times faster on this site https://bejamas.com/compare/vercel-vs-netlify, although now they're almost equal.

Perhaps it would be a good idea to update the site address in the repo and redirect the old address to the new one, as the old site still has code from two years ago. Although it's better to keep the old address if a maintainer still have a Netlify account.

Oct 24 '25 10:10 nakrovati

I see... Performances is not really an issue in this context.

The idea is only to enable auto deploy on this project, in order to deploy when a new PR is merged on master 👍

Will configure it ...

Oct 24 '25 13:10 waghanza