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

[Bug] 3.4.0 beta 无法启用 forkTSChecker #6230

Closed
urielvan opened this issue Mar 9, 2021 · 2 comments · Fixed by #6232
Closed

[Bug] 3.4.0 beta 无法启用 forkTSChecker #6230

urielvan opened this issue Mar 9, 2021 · 2 comments · Fixed by #6232
Assignees

Comments

@urielvan
Copy link

urielvan commented Mar 9, 2021

What happens?

配置项启用 forkTSChecker 无法正常启用插件

Mini Showcase Repository(REQUIRED)

https://github.com/urielvan/umi-fork-ts-bug

How To Reproduce

执行 npm run start 之后控制台中输出了错误信息,src/pages/index.tsx 中参数 foo 为隐式 any 类型,正常情况下应该被报错

internal/modules/cjs/loader.js:968
  throw err;
  ^

Error: Cannot find module 'D:\Code\fork-ts\node_modules\@umijs\deps\compiled\fork-ts-checker-webpack-plugin\TypeScriptReporterRpcService.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:965:15)
    at Function.Module._load (internal/modules/cjs/loader.js:841:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)

√ Webpack
  Compiled successfully in 3.14s

RpcIpcMessagePortClosedError: Process 3860 exited with code "1" [null]
Issues checking service aborted - probably out of memory. Check the `memoryLimit` option in the ForkTsCheckerWebpackPlugin configuration.
If increasing the memory doesn't solve the issue, it's most probably a bug in the TypeScript or EsLint.

Context

  • Umi Version: 3.4.0-beta6
  • Node Version: 12.18.3
  • Platform: windows 10
@ycjcl868
Copy link
Contributor

ycjcl868 commented Mar 9, 2021

@umijs/deps 没打进去

@sorrycc
Copy link
Member

sorrycc commented Mar 9, 2021

image
正常是这个报错对吧?

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

Successfully merging a pull request may close this issue.

3 participants