Description
The tsconfig.json has "strict": true but the build script (npm run compile) runs webpack directly without a separate type-check step. Webpack with ts-loader does not enforce strict type checking by default — it only transpiles. This means type errors can slip through.
Current State
// tsconfig.json has strict: true
// but compile runs: webpack --mode production
// which uses ts-loader without fork-ts-checker-webpack-plugin
Type errors that should be caught at build time are silently ignored.
Expected Behavior
Add a type-check step to the build process:
- Install
fork-ts-checker-webpack-plugin for in-bundle type checking, OR
- Add a separate
typecheck script: tsc --noEmit
- Run type checking in CI and before publishing
The vscode:prepublish script should include type checking:
"vscode:prepublish": "npm run typecheck && npm run compile && npm run lint"
Acceptance Criteria
Complexity
Trivial — adding a script and a devDependency, minor type fixes.
Points
100
Description
The
tsconfig.jsonhas"strict": truebut the build script (npm run compile) runs webpack directly without a separate type-check step. Webpack withts-loaderdoes not enforce strict type checking by default — it only transpiles. This means type errors can slip through.Current State
Type errors that should be caught at build time are silently ignored.
Expected Behavior
Add a type-check step to the build process:
fork-ts-checker-webpack-pluginfor in-bundle type checking, ORtypecheckscript:tsc --noEmitThe
vscode:prepublishscript should include type checking:Acceptance Criteria
npm run typecheckcatches TypeScript strict mode errorsComplexity
Trivial — adding a script and a devDependency, minor type fixes.
Points
100