OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
impress/package.json

54 lines
1.7 KiB
JSON
Raw Permalink Normal View History

Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
{
Set up eslint for wardrobe-2020 Ok cool, I have just not been running any of this since moving out of impress-2020, but now that we're doing serious JS work in here it's time to turn it back on!! 1. Install eslint and the plugins we use 2. Set up a `yarn lint` command 3. Set up a git hook via husky to lint on pre-commit 4. Fix/disable all the lint errors!
2023-11-02 18:03:15 -07:00
"name": "impress",
"private": true,
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
"dependencies": {
"@apollo/client": "^3.6.9",
"@chakra-ui/icons": "^1.0.4",
"@chakra-ui/react": "^1.6.0",
"@emotion/react": "^11.1.4",
"@emotion/styled": "^11.0.0",
Add Turbo to speed up the app, and set up for missing UJS features Oh right, we don't have Rails UJS going on anymore, which is what handled the confirmation prompts for deleting lists. Turbo is the more standard modern solution to that, and should speed up certain pageloads, so let's do it! Here I install the `turbo-rails` gem, then run `rails turbo:install` to install the `@hotwired/turbo-rails` npm package. Then I move `application.js` that's run all on pages but the outfit editor into our section of JS that gets run through the bundler, and add Turbo to it. I had to fix a couple tricky things: 1. The outfit editor page doesn't play nice with being swapped into the document, so I make it require a full page reload instead. 2. Prefetching the Sign In link can cause the wrong `return_to` address to be written to the `session`. (It's a GET request that does, ever so slightly, take its own actions, oops!) As a simple hacky answer, we disallow prefetching on that link. Haven't fixed up the UJS stuff for confirm prompts to use Turbo yet, that's next!
2024-03-13 13:43:48 -07:00
"@hotwired/turbo-rails": "^8.0.4",
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
"@loadable/component": "^5.12.0",
"@sentry/react": "^5.30.0",
Add AppProvider to wardrobe-2020 Hey the app runs now! How exciting! It doesn't run *correctly* but it renders at all!!
2023-08-10 18:09:10 -07:00
"@sentry/tracing": "^5.30.0",
Use the main app for outfit saving, not impress-2020 This came in a few parts! 1. Add meta tags to let us know we're logged in. 2. Install React Query, which has the data-loading sensibilities I like about Apollo without the GraphQL that has honestly been a drag. 3. Replace the outfit-loading and outfit-saving calls with API calls to the main app. 4. Update the main app's API calls to use our more flexible data constructs like "pose". Would've loved to do this more incrementally, but it's hard to! You can't split out outfit-loading and outfit-saving, or auth from any of that, or the state gets all out-of-sorts. Still, this is a good nugget we've pulled out all-in-all, and one that people have been asking for! Can maybe look to logged-in item search soon too, for own/want data?
2023-11-02 13:50:33 -07:00
"@tanstack/react-query": "^5.4.3",
Add AppProvider to wardrobe-2020 Hey the app runs now! How exciting! It doesn't run *correctly* but it renders at all!!
2023-08-10 18:09:10 -07:00
"apollo-link-persisted-queries": "^0.2.2",
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
"easeljs": "^1.0.2",
"esbuild": "^0.19.0",
"framer-motion": "^4.1.11",
"graphql": "^15.5.0",
"graphql-tag": "^2.12.6",
"immer": "^9.0.6",
"lru-cache": "^6.0.0",
Upgrade to React 18.2.0 Poked at the app and saw no breakages, I'm reasonably satisfied! I think the 17 -> 18 migration is designed to be pretty backwards-compatible, especially since I didn't bother to do the `createRoot` stuff yet, which is where more of the breaking things happen.
2023-11-01 20:15:30 -07:00
"react": "^18.2.0",
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
"react-autosuggest": "^10.0.2",
Upgrade to React 18.2.0 Poked at the app and saw no breakages, I'm reasonably satisfied! I think the 17 -> 18 migration is designed to be pretty backwards-compatible, especially since I didn't bother to do the `createRoot` stuff yet, which is where more of the breaking things happen.
2023-11-01 20:15:30 -07:00
"react-dom": "^18.2.0",
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
"react-icons": "^4.2.0",
Replace next/link with physical links All of these are links out of wardrobe-2020 now! We'll replace the router with react-router, but just for outfit state stuff.
2023-08-10 16:31:39 -07:00
"react-router-dom": "^6.15.0",
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
"react-transition-group": "^4.3.0",
"tweenjs": "^1.0.2"
},
Add Prettier to dev dependencies I'm trying out a new editor setup, and it noticed that Prettier isn't obviously installed! I think it makes sense to put it in dev deps, even if there's not a direct hook calling it—though tbh maybe I should add it to `yarn dev` somehow?
2023-10-24 16:37:06 -07:00
"devDependencies": {
Upgrade typescript-eslint dependencies When running linting for the first time in a while on my desktop machine (I didn't have the git hooks set up, oops!), I got some warnings about my version of Typescript being too recent for my version of `typescript-eslint`. Upgraded to latest! Linting still works.
2024-05-06 15:07:43 -07:00
"@typescript-eslint/eslint-plugin": "^7.8.0",
"@typescript-eslint/parser": "^7.8.0",
Set up eslint for wardrobe-2020 Ok cool, I have just not been running any of this since moving out of impress-2020, but now that we're doing serious JS work in here it's time to turn it back on!! 1. Install eslint and the plugins we use 2. Set up a `yarn lint` command 3. Set up a git hook via husky to lint on pre-commit 4. Fix/disable all the lint errors!
2023-11-02 18:03:15 -07:00
"eslint": "^8.52.0",
"eslint-plugin-jsx-a11y": "^6.8.0",
"eslint-plugin-react": "^7.33.2",
"eslint-plugin-react-hooks": "^4.6.0",
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"express": "^4.18.3",
Set up eslint for wardrobe-2020 Ok cool, I have just not been running any of this since moving out of impress-2020, but now that we're doing serious JS work in here it's time to turn it back on!! 1. Install eslint and the plugins we use 2. Set up a `yarn lint` command 3. Set up a git hook via husky to lint on pre-commit 4. Fix/disable all the lint errors!
2023-11-02 18:03:15 -07:00
"husky": "^8.0.3",
Split NeoPass dev server into main/backing servers
2024-03-13 13:00:27 -07:00
"node-fetch": "^3.3.2",
WIP: Add bin/neopass-server as test NeoPass server implementation Just a little mock server for use in development! Not referenced by anything yet.
2024-03-12 20:02:23 -07:00
"oauth2-mock-server": "^7.1.1",
Set up eslint for wardrobe-2020 Ok cool, I have just not been running any of this since moving out of impress-2020, but now that we're doing serious JS work in here it's time to turn it back on!! 1. Install eslint and the plugins we use 2. Set up a `yarn lint` command 3. Set up a git hook via husky to lint on pre-commit 4. Fix/disable all the lint errors!
2023-11-02 18:03:15 -07:00
"prettier": "^3.0.3",
"typescript": "^5.2.2"
Add Prettier to dev dependencies I'm trying out a new editor setup, and it noticed that Prettier isn't obviously installed! I think it makes sense to put it in dev deps, even if there's not a direct hook calling it—though tbh maybe I should add it to `yarn dev` somehow?
2023-10-24 16:37:06 -07:00
},
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
"scripts": {
Upgrade to Yarn 4.0.2 Unlike previous attempts to do future-Yarn, this seemed to just mostly go swimmingly, idk why! (I moved to a new computer and installed new Yarn without really thinking, and hey nice!) There was an issue where it was trying to do some glob expansion in one of the arguments for the `build` script, fixed! (Idk why Yarn has its own glob expansion and different from previous versions, but ok!)
2024-01-14 23:05:53 -08:00
"build": "esbuild app/javascript/*.* --bundle --sourcemap --outdir=app/assets/builds --public-path=/assets --asset-names='[name]-[hash].digested' --loader:.js=jsx --loader:.png=file --loader:.svg=file --loader:.min.js=text",
Build wardrobe-2020 JS during dev container setup Oh yeah right, let's `yarn install` and build as part of the `post-create.sh` script! I didn't have a command to do a one-time dev build of the assets yet (just one-time prod, or dev with reloading), so I added `yarn build:dev`!
2023-10-26 14:39:42 -07:00
"build:dev": "yarn build --public-path=/dev-assets",
Set up eslint for wardrobe-2020 Ok cool, I have just not been running any of this since moving out of impress-2020, but now that we're doing serious JS work in here it's time to turn it back on!! 1. Install eslint and the plugins we use 2. Set up a `yarn lint` command 3. Set up a git hook via husky to lint on pre-commit 4. Fix/disable all the lint errors!
2023-11-02 18:03:15 -07:00
"dev": "yarn build:dev --watch",
"lint": "eslint app/javascript",
"prepare": "husky install"
Update Yarn version & packages New install, new life!
2024-05-02 13:19:39 -07:00
},
"packageManager": "yarn@4.2.1"
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
}
Copy permalink