chore: setup eslint & prettier #3
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| /** @type {import('eslint').Linter.Config} */ | ||
| module.exports = { | ||
| parser: "@typescript-eslint/parser", | ||
| parserOptions: { | ||
| project: "tsconfig.json", | ||
| tsconfigRootDir: __dirname, | ||
| sourceType: "module", | ||
| }, | ||
| plugins: ["@typescript-eslint/eslint-plugin"], | ||
| extends: ["plugin:@typescript-eslint/recommended", "plugin:prettier/recommended"], | ||
| root: true, | ||
| env: { | ||
| node: true, | ||
| jest: true, | ||
| }, | ||
| ignorePatterns: [".eslintrc.js"], | ||
| rules: { | ||
| "@typescript-eslint/explicit-function-return-type": "off", | ||
| "@typescript-eslint/explicit-module-boundary-types": "off", | ||
| "@typescript-eslint/no-misused-promises": "error", | ||
| "@typescript-eslint/no-floating-promises": "error", | ||
|
Comment on lines
+20
to
+21
There was a problem hiding this comment. JAJAJAJAJA i had to search the flag |
||
| "@typescript-eslint/no-explicit-any": "error", | ||
| "@typescript-eslint/no-unsafe-assignment": "warn", | ||
| "@typescript-eslint/no-unsafe-argument": "warn", | ||
| "@typescript-eslint/no-unsafe-member-access": "error", | ||
| "@typescript-eslint/no-unsafe-return": "error", | ||
| "@typescript-eslint/no-unused-vars": [ | ||
| "error", | ||
| { argsIgnorePattern: "_+", ignoreRestSiblings: true }, | ||
| ], | ||
| "@typescript-eslint/prefer-as-const": "warn", | ||
| }, | ||
| }; | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| pnpm lint-staged && pnpm check-types |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| { | ||
| "arrowParens": "always", | ||
| "printWidth": 100, | ||
| "singleQuote": false, | ||
| "semi": true, | ||
| "trailingComma": "all", | ||
| "tabWidth": 4, | ||
| "plugins": ["@ianvs/prettier-plugin-sort-imports"], | ||
| "importOrder": [ | ||
| "<TYPES>", | ||
| "<THIRD_PARTY_MODULES>", | ||
| "", | ||
| "<TYPES>^@zkchainhub", | ||
| "^@zkchainhub/(.*)$", | ||
|
|
||
| "", | ||
| "<TYPES>^[.|..|~]", | ||
| "^~/", | ||
| "^[../]", | ||
| "^[./]" | ||
| ], | ||
| "importOrderParserPlugins": ["typescript", "decorators-legacy"], | ||
| "importOrderTypeScriptVersion": "5.4.5" | ||
| } | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,36 +1,50 @@ | ||
| { | ||
| "name": "ts-turborepo-boilerplate", | ||
| "version": "0.0.1", | ||
| "private": true, | ||
| "description": "", | ||
| "license": "MIT", | ||
| "author": "Wonderland", | ||
| "type": "module", | ||
| "scripts": { | ||
| "build": "turbo run build", | ||
| "check-types": "turbo run check-types", | ||
| "dev": "turbo run dev", | ||
| "format": "turbo run format", | ||
| "format:fix": "turbo run format:fix", | ||
| "preinstall": "npx only-allow pnpm", | ||
| "lint": "turbo run lint", | ||
| "lint:fix": "turbo run lint:fix", | ||
| "prepare": "husky", | ||
| "start": "turbo run start", | ||
| "test": "turbo run test", | ||
| "test:cov": "turbo run test:cov", | ||
| "test:integration": "turbo run test:integration" | ||
| }, | ||
| "lint-staged": { | ||
| "*": "prettier --write --ignore-unknown", | ||
| "*.js,*.ts,*.json": "eslint --fix", | ||
| "package.json": "sort-package-json" | ||
| }, | ||
| "devDependencies": { | ||
| "@commitlint/config-conventional": "19.4.1", | ||
| "@ianvs/prettier-plugin-sort-imports": "4.3.1", | ||
| "@types/node": "22.5.4", | ||
| "@typescript-eslint/eslint-plugin": "7.18.0", | ||
| "@typescript-eslint/parser": "7.18.0", | ||
| "commitlint": "19.4.1", | ||
| "eslint": "8.56.0", | ||
| "eslint-config-prettier": "9.1.0", | ||
| "eslint-plugin-prettier": "5.2.1", | ||
| "husky": "9.1.5", | ||
| "lint-staged": "15.2.10", | ||
| "prettier": "3.3.3", | ||
| "sort-package-json": "2.10.1", | ||
| "turbo": "2.1.1", | ||
| "typescript": "5.5.4" | ||
| }, | ||
| "packageManager": "[email protected]+sha256.46f1bbc8f8020aa9869568c387198f1a813f21fb44c82f400e7d1dbde6c70b40", | ||
| "engines": { | ||
| "node": "20" | ||
| } | ||
| } |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We were debating with @0xkenj1 about having explicit return types. I generally like the idea of being explicit but should we enforce it on the template though or are we going to be lenient on our base?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to me both are okay but if we're going to be explicit then makes sense to have it on, maybe just a warning to not be so strict
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @jahabeebs thoughts?