Go to file
saml33 86670e1b2f update share meta 2023-04-06 20:43:22 +10: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 wait to subscribe to stream if it isnt open yet 2023-03-31 20:14:59 -04:00
components fix trade form submit on button group 2023-04-06 13:49:47 +10:00
hooks list tokens from ui (#107) 2023-04-05 23:59:30 +02:00
pages update share meta 2023-04-06 20:43:22 +10:00
public update share meta 2023-04-06 20:43:22 +10:00
store list tokens from ui (#107) 2023-04-05 23:59:30 +02:00
styles merge main 2023-03-27 11:42:50 +11:00
types expand perp trade activity feed details 2023-04-05 14:21:01 +10:00
utils list tokens from ui (#107) 2023-04-05 23:59:30 +02: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 list tokens from ui (#107) 2023-04-05 23:59:30 +02:00
package.json list tokens from ui (#107) 2023-04-05 23:59:30 +02: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 list tokens from ui (#107) 2023-04-05 23:59:30 +02: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.