Release | Build Status |
---|---|
Edge | |
Latest |
This project was bootstrapped with Create Next App.
Find the most recent version of this guide here, and check out Next.js repo for the most up-to-date info on Next JS.
A docker-compose setup is available in the compose
folder.
Navigate to /compose
(cd ./compose
) and Follow the instructions found in compose/README.md
to start a local cluster of Argo Platform micro services.
- Install dependencies:
npm ci
- Set up environment: copy
.env.schema
to.env
and update environment accordingly. Out-of-the-box values are meant for local development. - Dev commands:
npm run dev
starts local dev servernpm run build
creates a production build.npm run force-resolutions
fixes vulnerable dependencies listed inpackage.json > resolutions
To keep commit messages consistent, we use gitmoji-cli, available as a dev dependency
npm run commit
will start interactive commit tool- configuring gitmoji-cli:
npm run gitmoji-config
npm run type-check
: trigger TypeScript type check for whole reponpm run type-check -- --watch
: runs the above with watch mode- Any
npm run type-check
triggerstsc
, so any flag layed out here can be used
- Any
- If using vscode (recommended),
tsc
can also be run as a task in the editor:Cmd+Shift+B
, then selecttsc:build - tsconfig.json
- This will report errors in vscode's
PROBLEMS
tab
/uikit
contains the reusable UI components for Argo.
- Creating a new component:
npm run create-component
- Important: If new dependencies are added for uikit, please include in
uikit/package.release.json
Increase version
under uikit/package.release.json
- Merge that change to
develop
, and let the Jenkins pipeline handle it
- Run
npm run build-uikit
which performs the following: - Run
npm run publish-uikit
to publish latest version to npm
uikit
components should not reference (import
) anything outside of theuikit
directory