m
/
metamask-extension
mirror of https://github.com/kremalicious/metamask-extension.git
1
0
Fork 0
Code
metamask-extension/tsconfig.json

40 lines
1021 B
JSON
Raw Permalink Normal View History

Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
{
"compilerOptions": {
"allowJs": true,
"allowSyntheticDefaultImports": true,
Add TypeScript migration dashboard (#13820) As we convert parts of the codebase to TypeScript, we will want a way to track progress. This commit adds a dashboard which displays all of the files that we wish to convert to TypeScript and which files we've already converted. The list of all possible files to convert is predetermined by walking the dependency graph of each entrypoint the build system uses to compile the extension (the files that the entrypoint imports, the files that the imports import, etc). The list should not need to be regenerated, but you can do it by running: yarn ts-migration:enumerate The dashboard is implemented as a separate React app. The CircleCI configuration has been updated so that when a new commit is pushed, the React app is built and stored in the CircleCI artifacts. When a PR is merged, the built files will be pushed to a separate repo whose sole purpose is to serve the dashboard via GitHub Pages (this is the same way that the Storybook works). All of the app code and script to build the app are self-contained under `development/ts-migration-dashboard`. To build this app yourself, you can run: yarn ts-migration:dashboard:build or if you want to build automatically as you change files, run: yarn ts-migration:dashboard:watch Then open the following file in your browser (there is no server component): development/ts-migration-dashboard/build/index.html Finally, although you shouldn't have to do this, to manually deploy the dashboard once built, you can run: git remote add ts-migration-dashboard git@github.com:MetaMask/metamask-extension-ts-migration-dashboard.git yarn ts-migration:dashboard:deploy
2022-08-09 22:16:08 +02:00
"baseUrl": ".",
Widen the number of test files that TS sees (#19403) Currently, all test files are excluded from TypeScript's purview. That means that if any test file fails to typecheck, we won't know about it. In fact if we were to remove all test files from the `exclude` list, then some files would indeed fail to be typechecked. At the moment all we care about is the unit test file for NetworkController. Due to how the `include`/`exclude` rules work in `tsconfig.json`, we can't "un-exclude" that file after it's excluded, so to fix this, we simply exclude fewer things. While we're at it, we also: - Add `esModuleInterop: true` to address warnings we sometimes see around imports - Add `noEmit: true` so that we can run `tsc` to test typechecking on its own without producing any compiled files (so that ESLint doesn't accidentally pick them up) - Clean up `tsconfig.json` slightly
2023-06-07 20:16:06 +02:00
"esModuleInterop": true,
Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
"inlineSources": true,
"isolatedModules": true,
"jsx": "react",
"lib": ["dom", "es2020"],
"moduleResolution": "node",
Widen the number of test files that TS sees (#19403) Currently, all test files are excluded from TypeScript's purview. That means that if any test file fails to typecheck, we won't know about it. In fact if we were to remove all test files from the `exclude` list, then some files would indeed fail to be typechecked. At the moment all we care about is the unit test file for NetworkController. Due to how the `include`/`exclude` rules work in `tsconfig.json`, we can't "un-exclude" that file after it's excluded, so to fix this, we simply exclude fewer things. While we're at it, we also: - Add `esModuleInterop: true` to address warnings we sometimes see around imports - Add `noEmit: true` so that we can run `tsc` to test typechecking on its own without producing any compiled files (so that ESLint doesn't accidentally pick them up) - Clean up `tsconfig.json` slightly
2023-06-07 20:16:06 +02:00
"noEmit": true,
Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
"noEmitOnError": true,
"outDir": "tsout",
"rootDir": ".",
"sourceMap": true,
Support translation in background code (#19650)
2023-06-20 14:44:11 +02:00
"strict": true,
"resolveJsonModule": true
Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
},
"exclude": [
TypeScript tooling fixes (#17513) * TypeScript tooling fixes * refine the dashboard ignore patterns
2023-02-01 17:51:12 +01:00
"**/jest-coverage/**/*",
"**/__mocks__/**/*",
"**/storybook-build/**/*",
Adding types file to Box component (#18009)
2023-03-08 18:35:16 +01:00
"**/*.stories.*",
Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
".storybook/**/*",
Widen the number of test files that TS sees (#19403) Currently, all test files are excluded from TypeScript's purview. That means that if any test file fails to typecheck, we won't know about it. In fact if we were to remove all test files from the `exclude` list, then some files would indeed fail to be typechecked. At the moment all we care about is the unit test file for NetworkController. Due to how the `include`/`exclude` rules work in `tsconfig.json`, we can't "un-exclude" that file after it's excluded, so to fix this, we simply exclude fewer things. While we're at it, we also: - Add `esModuleInterop: true` to address warnings we sometimes see around imports - Add `noEmit: true` so that we can run `tsc` to test typechecking on its own without producing any compiled files (so that ESLint doesn't accidentally pick them up) - Clean up `tsconfig.json` slightly
2023-06-07 20:16:06 +02:00
"app/scripts/controllers/*.test.ts",
"app/scripts/lib/**/*.test.ts",
Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
"builds/**/*",
"dist/**/*",
TypeScript tooling fixes (#17513) * TypeScript tooling fixes * refine the dashboard ignore patterns
2023-02-01 17:51:12 +01:00
"node_modules/**",
"development/ts-migration-dashboard/build/**/*",
Widen the number of test files that TS sees (#19403) Currently, all test files are excluded from TypeScript's purview. That means that if any test file fails to typecheck, we won't know about it. In fact if we were to remove all test files from the `exclude` list, then some files would indeed fail to be typechecked. At the moment all we care about is the unit test file for NetworkController. Due to how the `include`/`exclude` rules work in `tsconfig.json`, we can't "un-exclude" that file after it's excluded, so to fix this, we simply exclude fewer things. While we're at it, we also: - Add `esModuleInterop: true` to address warnings we sometimes see around imports - Add `noEmit: true` so that we can run `tsc` to test typechecking on its own without producing any compiled files (so that ESLint doesn't accidentally pick them up) - Clean up `tsconfig.json` slightly
2023-06-07 20:16:06 +02:00
"development/ts-migration-dashboard/intermediate/**/*",
"ui/**/*.test.js",
"ui/**/*.test.ts",
"ui/**/*.test.tsx"
Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
],
chore: Complete node16 upgrade (#15634) Follow-up from #15131
2022-08-19 16:35:52 +02:00
"extends": "@tsconfig/node16/tsconfig.json",
Widen the number of test files that TS sees (#19403) Currently, all test files are excluded from TypeScript's purview. That means that if any test file fails to typecheck, we won't know about it. In fact if we were to remove all test files from the `exclude` list, then some files would indeed fail to be typechecked. At the moment all we care about is the unit test file for NetworkController. Due to how the `include`/`exclude` rules work in `tsconfig.json`, we can't "un-exclude" that file after it's excluded, so to fix this, we simply exclude fewer things. While we're at it, we also: - Add `esModuleInterop: true` to address warnings we sometimes see around imports - Add `noEmit: true` so that we can run `tsc` to test typechecking on its own without producing any compiled files (so that ESLint doesn't accidentally pick them up) - Clean up `tsconfig.json` slightly
2023-06-07 20:16:06 +02:00
"include": ["app", "development", "shared", "types", "ui"]
Add TypeScript to the linting process (#13495) This commit allows developers to write TypeScript files and lint them (either via a language server in their editor of choice or through the `yarn lint` command). The new TypeScript configuration as well as the updated ESLint configuration not only includes support for parsing TypeScript files, but also provides some compatibility between JavaScript and TypeScript. That is, it makes it possible for a TypeScript file that imports a JavaScript file or a JavaScript file that imports a TypeScript file to be linted. Note that this commit does not integrate TypeScript into the build system yet, so we cannot start converting files to TypeScript and pushing them to the repo until that final step is complete.
2022-03-21 19:54:47 +01:00
}