✅ Disabling Type and Linting Error Checks

TypeScript helps you catch errors at compile time, which can save time and improve code quality, but can be challenging for those who are new to the language or who are used to the more dynamic nature of JavaScript. These sections show the steps required to disable type & lint checks on different levels.

Disabling Commit Checks

We run the pre-commit git hook which lints the staged files and doesn't let you commit if there is an linting error.

To disable this, go to the .husky/pre-commit file and comment out yarn lint-staged --verbose

- yarn lint-staged --verbose
+ # yarn lint-staged --verbose

Deploying to Vercel Without Any Checks

By default, Vercel runs type and lint checks before building your app. The deployment will fail if there are any type or lint errors.

To ignore these checks while deploying from the CLI, use:

yarn vercel:yolo

If your repo is connected to Vercel, you can set NEXT_PUBLIC_IGNORE_BUILD_ERROR to true in an environment variable.

Disabling GitHub Workflow

We have a GitHub workflow setup, checkout .github/workflows/ci.yml, which runs on every pull request and every push to the master branch. It runs the type, lint and build checks for the NextJS app and type checks the Move scripts. It also compiles and tests the Move package for Movement and Aptos.

To disable it, delete the .github/workflows/ci.yml file (or the whole .github directory).