Manav Rathi
0a01cac57b
Take 1 (incorrect)
2024-05-24 09:27:28 +05:30
Manav Rathi
7780c1c7b7
Move to the correct place
2024-05-23 19:29:56 +05:30
Manav Rathi
1a376a1a9b
Update deps
2024-05-21 11:52:01 +05:30
Manav Rathi
1856e344db
Remove unused clustering method
2024-05-16 11:03:03 +05:30
Manav Rathi
b9ffc2d5b6
yarn upgrade-interactive eslint-plugin-react-hooks
2024-05-15 15:28:58 +05:30
Manav Rathi
1f4bac8fac
Update build-deps
2024-05-15 15:27:05 +05:30
Manav Rathi
45183422e2
[web] Lint concurrently
2024-05-15 13:59:10 +05:30
Manav Rathi
d2b59565cb
Remove unnecessary dependency
2024-05-11 09:14:40 +05:30
Manav Rathi
6568cb19a9
f
2024-05-10 22:14:09 +05:30
Manav Rathi
7d56230b91
Move down
2024-05-09 20:44:52 +05:30
Manav Rathi
ac67566f45
Update react-dropzone
...
Release notes don't seem to have any breaking changes:
https://github.com/react-dropzone/react-dropzone/releases
Need to update to figure out where exactly the path property is coming from.
2024-05-09 10:03:03 +05:30
Manav Rathi
a0c5dd84c7
Add typings
2024-05-03 19:00:16 +05:30
Manav Rathi
e18731e625
yarn upgrade-interactive typescript and lints
2024-05-01 08:51:47 +05:30
Manav Rathi
1447d4976f
lint-fix and beautifuller
2024-04-24 18:48:44 +05:30
Manav Rathi
af79db90d0
Doesn't work for us yet
...
Current version throws
Module build failed: UnhandledSchemeError: Reading from "node:buffer" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
See: https://github.com/sindresorhus/file-type/issues/502
There are ways around by using polyfills, e.g.
- https://stackoverflow.com/questions/76500464/issues-while-using-gradio-client-in-next-js/76522223#76522223
- https://github.com/vercel/next.js/discussions/33982
but since no functional changes in the detection that impact us have been made,
stay back at the old version for now.
2024-04-24 18:44:09 +05:30
Manav Rathi
38e18f29bd
Update file-type dependency and move it to its correct package.json
...
Refs:
- https://github.com/sindresorhus/file-type/releases/tag/v17.0.0
Went through the release notes since v16 to check that none of the MIME types we
care about have changed.
2024-04-24 18:27:30 +05:30
Manav Rathi
3172104578
Start using @/media's version
2024-04-17 10:08:08 +05:30
Manav Rathi
4b9446a9b0
Create a package to share code between photos and cast
2024-04-17 09:47:28 +05:30
daviddeepan
2a9060bd39
css-alignment-issue-page-gallery
2024-04-14 13:53:00 +05:30
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
Manav Rathi
e6905577c6
Remove blazeface-back
2024-04-11 11:17:15 +05:30
Manav Rathi
52342a23cb
Remove tensorflow packages
...
yarn workspace photos remove "@tensorflow-models/coco-ssd" "@tensorflow/tfjs-backend-cpu" "@tensorflow/tfjs-backend-webgl" "@tensorflow/tfjs-converter" "@tensorflow/tfjs-core" "@tensorflow/tfjs-tflite"
2024-04-10 21:29:23 +05:30
Manav Rathi
5339b1aa89
Merge
2024-04-08 20:39:53 +05:30
Manav Rathi
3cb51184b3
[web] Add required transitive dependency of MUI datepicker
...
Previously this was coming from react-datepicker that was otherwise unused and thus removed.
Use the same major version as we had previously.
Ref:
https://stackoverflow.com/questions/71037974/module-not-found-error-cant-resolve-date-fns-adddays-in-c-users
2024-04-07 09:26:52 +05:30
Manav Rathi
d317da6536
Remove unused package react-datepicker
...
+ another unused type
+ an transitive from code
2024-04-07 08:42:27 +05:30
Manav Rathi
4b074f4475
Fix the CSS for cast
2024-04-06 19:15:42 +05:30
Manav Rathi
121df66ada
Cleanup
2024-04-06 11:19:14 +05:30
Manav Rathi
a98a29800b
[web] Bundle translations but load them lazily
...
Refs:
- https://github.com/i18next/i18next-resources-to-backend
- https://stackoverflow.com/questions/77251750/how-to-implement-lazy-loading-translations-in-i18next-with-react
- https://github.com/i18next/react-i18next/issues/525
- https://gist.github.com/SimeonC/6a738467c691eef7f21ebf96918cd95f
- https://www.i18next.com/overview/plugins-and-utils
2024-04-06 11:06:29 +05:30
Manav Rathi
d9d03d8451
Add schema validation of the response
2024-04-04 16:12:39 +05:30
Manav Rathi
87dc7d76ca
Remove middleman package, to get it to compile
2024-04-04 11:36:20 +05:30
Manav Rathi
b3a86874db
yarn.lock
2024-04-02 20:47:35 +05:30
Manav Rathi
5c1ed5be8f
Restructure eslint config
2024-04-02 20:44:57 +05:30
Manav Rathi
14fde54d87
Not really
2024-04-02 20:04:23 +05:30
Manav Rathi
9b27cac465
Remove @emotion/server
...
It is not mentioned as a dependency in the SSR page
> For v10 and above, SSR just works in Next.js.
>
> https://emotion.sh/docs/ssr
Tested by - yarn dev, yarn preview:photos
2024-04-01 16:05:17 +05:30
Manav Rathi
7248a226bc
Remove bootstrap
2024-04-01 15:35:45 +05:30
Manav Rathi
0f2181c09b
Remove more legacy ml code
2024-03-31 18:41:15 +05:30
Manav Rathi
3890373d4a
Try pure-react-carousel as a replacement of bootstrap's Carousel
2024-03-31 16:45:46 +05:30
Manav Rathi
1f6b9030ff
[web] Fix nightly build
...
This was accidentally an ancient version of axios when importing from the older
repo - update it to what the rest of the code uses (via the shared package).
2024-03-29 09:11:28 +05:30
Manav Rathi
8f0ef055c5
[web] Make the imported payments code feel at home in the new monorepo
...
- Use the shared yarn monorepo configuration
- styled-components => emotion (since that's what the rest of the code uses)
- Remove Sentry (since it's gone elsewhere)
2024-03-28 11:40:22 +05:30
Manav Rathi
fc3aea7694
[web] Update yarn.lock
2024-03-19 11:24:42 +05:30
httpjamesm
d9b1081849
Merge branch 'main' into feature/web-passkey-recovery
2024-03-12 13:57:57 -04:00
Manav Rathi
70cddfdf0b
[web] Remove Sentry
...
Sentry has a measurable impact on page load, a metric that I'm keen to
improve. Apparently by default it loses us 8-9 page speed points, though that
can be reduced to 3-4
(https://github.com/getsentry/sentry-javascript/issues/9179 ).
All of this is doable, but there are bigger tasks to deal with. This is not to
say that Sentry won't be useful again at some point, when we have time to deal
with it better. But right now, we discussed that it's just better to remove
Sentry instead of piling on to the sunk cost.
2024-03-12 13:24:33 +05:30
httpjamesm
438387a4cb
fix: remove organize imports dep
2024-03-11 13:55:44 -04:00
httpjamesm
27a1d420db
feat: configure passkey recovery on passkeys click
2024-03-11 13:24:25 -04:00
httpjamesm
69048844d7
fix: add prettier-plugin-organize-imports
2024-03-11 13:10:27 -04:00
Manav Rathi
e15c7e1642
Move into web/
2024-03-01 12:21:07 +05:30
