Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot find module issue while using on a webpack.config.TS file #359

Closed
junalmeida opened this issue Nov 21, 2019 · 3 comments
Closed

Cannot find module issue while using on a webpack.config.TS file #359

junalmeida opened this issue Nov 21, 2019 · 3 comments
Labels

Comments

@junalmeida
Copy link

Current behavior

image

Expected behavior

Typings should be found by the editor.

Steps to reproduce the issue

Add package and run yarn install

Issue reproduction repository

None yet

Environment

  • fork-ts-checker-webpack-plugin: 3.1.0
  • typescript: 3.7.2
  • tslint: 5.14.0
  • webpack: 4.29.0
  • os: Windows
@junalmeida junalmeida added the bug label Nov 21, 2019
@phryneas
Copy link
Contributor

This means that the TSServer run by your IDE cannot find fork-ts-checker-webpack-plugin. This can have plenty of reasons (most likely misconfiguration of moduleResolution, typeRoots or types in your tsconfig.json - or it is actually not installed), but it definitely is not a bug of fork-ts-checker-webpack-plugin.

Please re-check your setup, and if you really can't resolve this create a reproducible minimal repository so we can help you fix it.

@junalmeida
Copy link
Author

@phryneas ok, let me show you my setup:

package.json
image

node-modules
image

tsconfig.json

"module": "commonjs",
"target": "es5",
"moduleResolution": "node",
"typeRoots": [ "./node_modules/@types", "./Content/src/custom_typings" ]

There is no types node.

@piotr-oles piotr-oles mentioned this issue Apr 18, 2020
26 tasks
@piotr-oles
Copy link
Collaborator

@junalmeida
Please try fork-ts-checker-webpack-plugin@alpha - I've published a new version which should resolve this issue 🚀
I will close this issue to clean-up the backlog. If this release didn't solve the issue, we can re-open this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants