Go to file
silas-x 34720de587 add prettier check 2023-01-26 09:57:27 +00:00
.github/workflows add prettier check 2023-01-26 09:57:27 +00:00
.husky add prettier check 2023-01-26 09:57:27 +00:00
apis remove console logs 2023-01-20 08:53:15 -05:00
components prettier 2023-01-26 09:56:32 +00:00
hooks improve use query config options 2023-01-20 11:13:03 -05:00
pages prettier 2023-01-26 09:56:32 +00:00
public add activity fee tooltip 2023-01-23 15:25:43 +11:00
store remove console logs 2023-01-20 08:53:15 -05:00
styles brighter red orderbook on dark theme 2023-01-17 11:36:47 -05:00
types fix trade history 2023-01-18 23:35:57 -05:00
utils remove show/hide account values 2023-01-24 09:52:59 +11:00
vendor
.eslintignore
.eslintrc.json
.gitignore
.prettierignore
.prettierrc
.yarnrc deny scripts 2023-01-25 15:02:51 +00:00
.yarnrc.yml deny scripts 2023-01-25 15:02:51 +00:00
LICENSE
README.md readme updates 2023-01-26 09:57:02 +00:00
next-env.d.ts
next-i18next.config.js
next.config.js bonk and dai fixes 2023-01-05 15:10:24 -05:00
package.json add prettier check 2023-01-26 09:57:27 +00:00
postcss.config.js
tailwind.config.js make bottom bar brighter 2023-01-22 20:54:07 +11:00
tsconfig.json add expand all collapse all to dashboard 2023-01-16 17:33:44 -05:00
yarn.lock dep update 2023-01-25 22:48:52 +00:00

README.md

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

Working with dependencies

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)

The allowScripts configuration in package.json:

  • There are two ways to configure script policies: ⋅⋅* Update the allow-scripts section manually by adding the missing package in the allowScripts section in package.json ⋅⋅* 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.