You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you so much for providing a very useful loader. For the most part it works really well, and has boosted my productivity substantially. I am having a problem, and would definitely appreciate your input in trying to figure out a fix/workaround, or guidance in the case I may be doing something wrong.
I have an npm package (A) that hosts an app that is bundled via webpack. When adding tslint-loader to my webpack builds, it works nicely.
Separately, I have a library as an npm package (B) that A consumes. Oftentimes, I may do development with both of them at the same time. I will use npm link to create a symlink between B and its independency inside A's node_modules folder. This workflow does not work for tslint-loader, as I get the following error:
ERROR in ../relative/path/to/failing/typescript/file.ts
Module build failed: FatalError:
Invalid source file: /Absolute/path/to/failing/typescript/file.ts. Ensure that the files supplied to lint have a .ts, .tsx, .d.ts, .js or .jsx extension.
at new FatalError (/Absolute/path/to/package/A/node_modules/tslint/lib/error.js:27:28)
at Linter.getSourceFile (/Absolute/path/to/package/A/node_modules/tslint/lib/linter.js:222:23)
at Linter.lint (/Absolute/path/to/package/A/node_modules/tslint/lib/linter.js:96:31)
at lint (/Absolute/path/to/package/A/node_modules/tslint-loader/index.js:70:10)
at Object.module.exports (/Absolute/path/to/package/A/node_modules/tslint-loader/index.js:140:3)
@ ../relative/path/to/failing/typescript/file.ts 22:0-45
The error in the linters only happens when I have type-checking enabled.
The error doesn't happen if I run the tslint command directly, i.e.
First of all, thank you so much for providing a very useful loader. For the most part it works really well, and has boosted my productivity substantially. I am having a problem, and would definitely appreciate your input in trying to figure out a fix/workaround, or guidance in the case I may be doing something wrong.
I have an npm package (A) that hosts an app that is bundled via webpack. When adding
tslint-loader
to my webpack builds, it works nicely.Separately, I have a library as an npm package (B) that A consumes. Oftentimes, I may do development with both of them at the same time. I will use
npm link
to create a symlink between B and its independency inside A's node_modules folder. This workflow does not work fortslint-loader
, as I get the following error:The error in the linters only happens when I have type-checking enabled.
The error doesn't happen if I run the tslint command directly, i.e.
The loader is using the same tslint.json and tsconfig.json files.
Let me know if I could provide more information.
The text was updated successfully, but these errors were encountered: