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
7ad4069b99
hobgoblins
2024-04-30 10:23:33 +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
df483b0755
lint
2024-04-17 12:37:18 +05:30
Manav Rathi
4b9446a9b0
Create a package to share code between photos and cast
2024-04-17 09:47:28 +05:30
Manav Rathi
56d04066ea
sfn
2024-04-13 20:38:29 +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
7deb0dca8e
Fix lint
2024-04-13 13:17:42 +05:30
Manav Rathi
6a3f4baed3
Enhance
2024-04-13 07:30:32 +05:30
Manav Rathi
8020d83ced
Fix crowdin paths
2024-04-06 11:30:31 +05:30
Manav Rathi
e53c923675
Lint fix + update URL
2024-04-04 15:44:03 +05:30
Manav Rathi
39228270c1
Deploy
2024-04-04 15:40:17 +05:30
Manav Rathi
f10f751a2f
Inline local storage calls
...
The methods are trivial, and we cannot centralize the keys since they will be
different for different apps. So an abstraction for this is not beneficial.
Also move the next specific dev build check to @/next
2024-04-03 14:21:11 +05:30
Manav Rathi
ad6dea2ecb
prettier markdown
2024-04-03 13:39:44 +05:30
Manav Rathi
a689aca4a6
Remove the eslint stuff from docs
...
(trying to remove the eslint-disables throughout)
2024-04-03 13:26:46 +05:30
Manav Rathi
26b35cec9e
Merge @/ui into @/next
2024-04-02 19:58:42 +05:30
Manav Rathi
eced463f6f
Investigate and explain why component selectors don't work with Next vanilla
...
Refs:
- https://github.com/mui/material-ui/issues/27380#issuecomment-928973157
- https://codesandbox.io/s/hopeful-browser-4q17t5?file=/README.md
- https://mui.com/system/styled/#how-to-use-components-selector-api
- https://github.com/vercel/next.js/issues/46973
2024-04-01 16:43:10 +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
6b56c28870
Mark vscode-styled-components optional
2024-03-31 17:07:48 +05:30
Manav Rathi
9ec68ecd3d
Mention vscode-styled-components
2024-03-31 17:04:38 +05:30
Manav Rathi
5810d2b762
Add yarn preview:*
2024-03-30 18:06:58 +05:30
Manav Rathi
212b2663d0
Add payments deployment scripts
2024-03-28 17:42:54 +05:30
Manav Rathi
24176d8c40
Document a few more dependencies
2024-03-26 21:42:48 +05:30
Manav Rathi
e4684b22df
Move out the electron-builder config to separate file
2024-03-19 19:17:01 +05:30
Manav Rathi
a9557df240
Add preview deployment docs
2024-03-12 10:08:52 +05:30
Manav Rathi
849b61c5cf
Document some and fix the path
2024-03-11 17:29:39 +05:30
Manav Rathi
6fdfa24e89
Document translation
2024-03-11 15:30:24 +05:30
Manav Rathi
290196ee9e
Add fixed nightly mappings
2024-03-08 16:36:06 +05:30
Manav Rathi
2d14cc5899
Mention fast forwards
2024-03-08 16:29:35 +05:30
Manav Rathi
0b585ce3a5
Update the documentation
2024-03-08 15:40:35 +05:30
Manav Rathi
8058d2bfd4
Add production deployments
2024-03-08 15:20:16 +05:30
Manav Rathi
215e89427d
[WIP] [docs] Deploy docs ( #742 )
...
Add a GitHub workflow to deploy docs. If this works, will start using
this same approach for the other web apps in our repo.
2024-03-08 13:30:28 +05:30
Manav Rathi
2eb95ab215
Move the docs deployment to the new project, its final resting place
2024-03-08 13:26:41 +05:30
Manav Rathi
9e4f4c4670
Document the need for yarn classic
2024-03-08 13:11:04 +05:30
Manav Rathi
05d13979db
Remove GitHub deployments
...
Not integrating GitHub deployments for now since creating a deployment
(anywhere) causes "This branch has not been deployed" message to appear on
unrelated branches.
Also, the Discord /github webhook doesn't support deployment status events
anyway - Discord accepts and responds to the webhook with a 204 but it doesn't
appear in the channel. This is not a big issue, we can easily massage the
payload ourselves, but just mentioning this for posterity. Refs:
* [Corresponding issue on Discord](https://github.com/discord/discord-api-docs/issues/6203#issuecomment-1608151265 )
* [A general recipe](https://gist.github.com/jagrosh/5b1761213e33fc5b54ec7f6379034a22 )
---
For deleting the existing deployment I had to
```
gh api /repos/ente-io/ente/deployments --jq=".[].id"
gh api --method DELETE -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" "/repos/ente-io/ente/deployments/1375794893"
```
This helpful hint taken from https://github.com/orgs/community/discussions/46375 . Thanks!
2024-03-08 12:30:58 +05:30
Manav Rathi
e47bcf2774
Merge for now
2024-03-08 12:05:12 +05:30
Manav Rathi
4da96a3b76
Add the workflow
2024-03-08 11:19:04 +05:30
Manav Rathi
e3118ee7b0
Start adding notes
2024-03-08 10:37:40 +05:30
Manav Rathi
f199ce0e83
Update deployment instructions
2024-03-06 11:44:09 +05:30
Manav Rathi
9d55b9936d
Document NODE_VERSION
2024-03-06 11:09:19 +05:30
Ikko Eltociear Ashimine
e13edc7486
Update dev.md
...
minor fix
2024-03-05 00:11:27 +09:00
Manav Rathi
a7dbd32bc9
Update mobile/ to account for new monorepo structure
2024-03-02 11:47:47 +05:30
Manav Rathi
d869bd645f
Update web/ to account for new monorepo structure
2024-03-02 10:13:51 +05:30
Manav Rathi
e15c7e1642
Move into web/
2024-03-01 12:21:07 +05:30
