beenull/ente
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
ente/web/package.json

39 lines
1.8 KiB
JSON
Raw Normal View History

Voila!
2020-09-09 21:09:51 +00:00
{
fix: rename monorepo to ente-web
2023-04-29 00:29:57 +00:00
"name": "ente-web",
next export is deprecated in Next 14
2024-02-16 15:59:29 +00:00
"version": "0.0.0",
feat: monorepo, turbo config, minimal pkgs
2023-04-18 21:29:40 +00:00
"private": true,
Fix pkg dependency
2023-05-29 02:06:02 +00:00
"workspaces": [
next export is deprecated in Next 14
2024-02-16 15:59:29 +00:00
"apps/*",
"packages/*"
Fix pkg dependency
2023-05-29 02:06:02 +00:00
],
feat: monorepo, turbo config, minimal pkgs
2023-04-18 21:29:40 +00:00
"scripts": {
Add shortcuts
2024-02-22 06:52:07 +00:00
"build": "yarn build:photos",
Fix build
2024-02-17 05:46:37 +00:00
"build:accounts": "yarn workspace accounts next build",
"build:auth": "yarn workspace auth next build",
"build:cast": "yarn workspace cast next build",
Remove Turbo - yarn classic workspaces already do what we need - The main benefit of turbo, the cache, is already disabled on dev builds. On production builds, turbo doesn't support `next build` (this is mentioned in Vercel's docs). - We're not using their remote cache - Maybe there is a monorepo size when the yarn workspace approach gets unwieldly, but I feel we're not near that point. Will bring it back if it gets missed.
2024-02-17 03:41:53 +00:00
"build:photos": "yarn workspace photos next build",
Update the URLs for opening new deployment PRs Note that the three dot syntax is needed, the two dot compare doesn't open a pull request. Ref: - https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request - https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests#three-dot-and-two-dot-git-diff-comparisons
2024-03-06 06:48:10 +00:00
"deploy:accounts": "open 'https://github.com/ente-io/ente/compare/deploy/accounts...main?quick_pull=1&title=[web]+Deploy+accounts&body=Deploy+accounts.ente.io'",
"deploy:auth": "open 'https://github.com/ente-io/ente/compare/deploy/auth...main?quick_pull=1&title=[web]+Deploy+auth&body=Deploy+auth.ente.io'",
"deploy:cast": "open 'https://github.com/ente-io/ente/compare/deploy/cast...main?quick_pull=1&title=[web]+Deploy+cast&body=Deploy+cast.ente.io'",
"deploy:photos": "open 'https://github.com/ente-io/ente/compare/deploy/photos...main?quick_pull=1&title=[web]+Deploy+photos&body=Deploy+web.ente.io'",
Add shortcuts
2024-02-22 06:52:07 +00:00
"dev": "yarn dev:photos",
Remove Turbo - yarn classic workspaces already do what we need - The main benefit of turbo, the cache, is already disabled on dev builds. On production builds, turbo doesn't support `next build` (this is mentioned in Vercel's docs). - We're not using their remote cache - Maybe there is a monorepo size when the yarn workspace approach gets unwieldly, but I feel we're not near that point. Will bring it back if it gets missed.
2024-02-17 03:41:53 +00:00
"dev:accounts": "yarn workspace accounts next dev",
prettier-plugin-packagejson
2024-02-24 09:16:02 +00:00
"dev:albums": "yarn workspace photos next dev -p 3002",
Remove Turbo - yarn classic workspaces already do what we need - The main benefit of turbo, the cache, is already disabled on dev builds. On production builds, turbo doesn't support `next build` (this is mentioned in Vercel's docs). - We're not using their remote cache - Maybe there is a monorepo size when the yarn workspace approach gets unwieldly, but I feel we're not near that point. Will bring it back if it gets missed.
2024-02-17 03:41:53 +00:00
"dev:auth": "yarn workspace auth next dev",
"dev:cast": "yarn workspace cast next dev",
"dev:photos": "yarn workspace photos next dev",
"lint": "yarn prettier --check . && yarn workspaces run eslint .",
Add a lint-fix command
2024-02-16 10:50:16 +00:00
"lint-fix": "yarn prettier --write . && yarn workspaces run eslint --fix ."
feat: monorepo, turbo config, minimal pkgs
2023-04-18 21:29:40 +00:00
},
prettier-plugin-packagejson
2024-02-24 09:16:02 +00:00
"resolutions": {
"@sentry/cli": "1.75.0",
"libsodium": "0.7.9"
},
feat: monorepo, turbo config, minimal pkgs
2023-04-18 21:29:40 +00:00
"devDependencies": {
Fix `yarn workspace photos add foo` This was likely happening because the package versions in the top level package.json and the eslint-config package.json were different. I've synced them for now. > On a longer time frame, the idea is not have such conflicting cases, and remove mostly all the top level package.json dependencies and for the rest rely on them solely being in the top level package.json and not duplicated in two places.
2024-02-21 15:42:11 +00:00
"eslint": "^8",
Update to Prettier 3
2024-02-22 06:06:17 +00:00
"prettier": "^3",
fix: add prettier-plugin-organize-imports
2024-03-11 17:10:27 +00:00
"prettier-plugin-organize-imports": "^1.0.0",
Update to latest emotion yarn upgrade "@emotion/react" "@emotion/server" "@emotion/styled" --latest This is to pull in the bugfix for this issue: https://github.com/emotion-js/emotion/issues/3049
2024-02-22 06:37:16 +00:00
"typescript": "^5"
Revert "migrate to yarn berry" This reverts commit 8fdac05728a22075fee61801f14c4dae9f856c46.
2023-11-17 08:50:52 +00:00
}
fix: too many fixes
2023-04-29 15:16:40 +00:00
}
Reference in a new issue Copy permalink