Last 12 weeks · 0 commits
4 of 6 standards met
is not enabled in this config, but I wanted to open an issue to document it in case you or anyone thinks about adding it. Given the comparison table with the lint rule in https://typescript-eslint.io/rules/consistent-type-imports/#comparison-with-importsnotusedasvalues--verbatimmodulesyntax (particularly the auto-fix ability) I think it's best to _not_ enable . Particularly noteworthy: Because there are some differences, using both this rule and verbatimModuleSyntax at the same time can lead to conflicting errors. As such we recommend that you only ever use one or the other -- never both.
May be time? Import attributes are live: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import/with#browser_compatibility Node.js 20.10 (Release date: 2023-11-22) Chrome 123 (Release date: 2024-03-19) Safari 17.2 (Release date: 2023-12-11) Firefox 138 (Release date: 2025-04-29) Some useful info: https://www.typescriptlang.org/docs/handbook/modules/reference.html#the-module-compiler-option
Repository: sindresorhus/tsconfig. Description: Shared TypeScript config for my projects Stars: 377, Forks: 32. License: MIT. Topics: config, npm-package, tsconfig, typescript. Latest release: v8.1.0 (9mo ago). Open PRs: 0, open issues: 4. Last activity: 9mo ago. Community health: 71%. Top contributors: sindresorhus, fregante, EdJoPaTo, felixfbecker, Rokt33r, mgenware, zanminkian, janriemer.