The 2020 Next.js rewrite, now being merged into impress!
Find a file
Matchu 214a93008b don't cache poses for Support tool
I noticed in prod that the Vercel edge cache can show old data in the Support tool right after you edit it and reload the page, which is super confusing!

In this change, we stop caching the endpoint we use for Support tools, so that the Support tools always feel real-time and trustworthy. (The standard pose picker might still be cached, so it could be a bit confusing for that to be out of sync, but at least you can toggle into Support mode and see that your changes happened _there_, so you don't panic that they're _gone_.)
2020-08-31 01:17:18 -07:00
.vscode create ItemsAndSearchPanel, simplify search refs 2020-04-26 00:37:58 -07:00
api log uploadLayerImage support actions 2020-08-26 19:12:43 -07:00
public use block behavior for lower-priority fonts 2020-05-18 00:59:10 -07:00
scripts Build cached zones, stop querying on server 2020-08-19 17:50:05 -07:00
src don't cache poses for Support tool 2020-08-31 01:17:18 -07:00
.gitignore add .vercel to .gitignore 2020-07-02 14:12:36 -07:00
config-overrides.js enable Fast Refresh 2020-07-22 21:03:04 -07:00
dev-todos.txt change validPetPoses bit order, add dims to blob 2020-05-03 13:03:02 -07:00
package.json Build cached zones, stop querying on server 2020-08-19 17:50:05 -07:00
README.md move to vercel now function api structure 2020-04-22 13:03:32 -07:00
setup-mysql-user.sql Support can label pet poses! 2020-08-31 00:32:17 -07:00
yarn.lock create cache-asset-manifests script 2020-08-17 18:23:39 -07:00

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

yarn eject

Note: this is a one-way operation. Once you eject, you cant go back!

If you arent satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point youre on your own.

You dont have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldnt feel obligated to use this feature. However we understand that this tool wouldnt be useful if you couldnt customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

yarn build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify