Go to file
saml33 9e7a4ebeac sort spot market stats table 2023-03-11 22:01:47 +13:00
.github/workflows chore: prettier 2023-01-26 15:30:54 +00:00
.husky reorder husky precommit 2023-02-13 22:35:07 -05:00
apis track market ids for trading view subscriptions 2023-03-10 10:49:22 -05:00
components sort spot market stats table 2023-03-11 22:01:47 +13:00
hooks prompt for refresh on new build 2023-03-05 15:33:57 -05:00
pages improve open orders display 2023-03-08 19:34:13 -05:00
public update side nav links 2023-03-08 14:24:46 -05:00
store improve open orders display 2023-03-08 19:34:13 -05:00
styles use normal font variant 2023-03-06 23:27:00 +11:00
types turn on lint errors for typescript any 2023-02-28 02:20:11 -05:00
utils revert change to load last account and bump local storage key version 2023-03-08 12:53:48 -05:00
vendor
.eslintignore
.eslintrc.json turn on lint errors for typescript any 2023-02-28 02:20:11 -05:00
.gitignore
.prettierignore add network concurrency for vercel builds 2023-01-28 14:41:13 -05:00
.prettierrc
.yarnrc auto pin deps going forward 2023-01-26 12:32:11 +00:00
.yarnrc.yml deny scripts 2023-01-25 15:02:51 +00:00
LICENSE
README.md separate dupe check and readme 2023-01-26 15:30:18 +00:00
next-env.d.ts
next-i18next.config.js
next.config.js prompt for refresh on new build 2023-03-05 15:33:57 -05:00
package.json extend dashboard 2023-03-01 14:16:07 +01:00
postcss.config.js
tailwind.config.js update onboarding intro copy 2023-03-08 10:54:13 +11:00
tsconfig.json use latest v4 npm pkg 2023-02-19 15:52:25 -05:00
yarn.lock upgrade client 2023-03-07 13:13:52 +01:00

README.md

This is a Next.js project bootstrapped with create-next-app.

Dependency Management

When updating dependencies, there are various files that must be kept up-to-date. Newly added, or updated dependencies can introduce unwanted/malicious scripts that can introduce risks for users and/or developers. The lavamoat allow-scripts feature allows us to deny by default, but adds some additional steps to the usual workflow.

yarn.lock:

  • Instead of running yarn or yarn install, run yarn setup to ensure the yarn.lock file is in sync and that dependency scripts are run according to the allowScripts policy (set in packages.json)
  • If lavamoat detects new scripts that are not explicitely allowed/denied, it'll throw and error with details (see below)
  • Running yarn setup will also dedupe the yarn.lock file to reduce the dependency tree. Note CI will fail if there are dupes in yarn.lock!

The allowScripts configuration in package.json:

  • There are two ways to configure script policies:
    1. Update the allow-scripts section manually by adding the missing package in the allowScripts section in package.json
    2. Run yarn allow-scripts auto to update the allowScripts configuration automatically
  • Review each new package to determine whether the install script needs to run or not, testing if necessary.
  • Use npx can-i-ignore-scripts to help assessing whether scripts are needed

Getting Started

First, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.