Manav Rathi 64231c73f1
[web] Add ESLint to enforce HMR how vite likes it
Configuration changes taken from the vite starter (react-ts).

From the vite docs (https://github.com/vitejs/vite-plugin-react-swc?tab=readme-ov-file#consistent-components-exports)

> For React refresh to work correctly, your file should only export React components.
>
> If an incompatible change in exports is found, the module will be invalidated.
> To make it easier to export simple constants alongside your component the module
> is only invalidated when their value changes.

While we're not currently using vite for our main apps, it would be worthwhile
to write code in a way that a future migration to it is painless if needed.

About the what and the why, the Gatsby docs are illuminating:
https://www.gatsbyjs.com/docs/reference/local-development/fast-refresh/#how-it-works

Some other refs:
- https://github.com/ArnaudBarre/eslint-plugin-react-refresh
- https://github.com/vitejs/vite/discussions/4577#discussioncomment-1161007
- https://github.com/vitejs/vite-plugin-react/issues/34
2024-04-13 18:38:24 +05:30
..
2024-04-04 15:44:03 +05:30
2024-04-03 13:39:44 +05:30
2024-03-11 15:30:24 +05:30
2024-03-11 17:29:39 +05:30
2024-04-13 13:17:42 +05:30
2024-04-06 11:30:31 +05:30
2024-04-03 13:39:44 +05:30

Developer docs

If you just want to run Ente's web apps locally or develop them, you can do

yarn install
yarn dev

The docs in this directory provide more details that some developers might find useful.