Closed aaronmcdavid closed 1 year ago
The TypeError: config.logger.error is not a function
seems to be an issue on create-react-scripts and fork-ts-checker-webpack-plugin integration - it looks like someone pass custom formatter option with a formatter that doesn't implement error method.
The TypeError: Cannot set property mark of #<Object> which has only a getter
is also weird - it's not coming from 7.3.0 (there is no connectTypeScriptPerformance
function - it's from older version of the plugin). It looks like you might have different versions of the plugin installed simultaneously and your webpack instance picks up the older one.
I see the TypeError: Cannot set property mark of #<Object> which has only a getter
in version 6.5.2
the last one with eslint support (the performance loss by switching to the main eslint plugin was too huge).
Any chance of updating the 6.5.x
branch to resolve this?
I hacked it locally (mostly commented out logging stuff) and was able to get things to work, but I'm not sure what I actually disabled/lost by doing that.
The typescript performance stuff is not important - it's only for debugging purposes. I don't have time this week to fix that, feel free to create a PR if you have a fix :)
@piotr-oles I opened https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/pull/803
:tada: This issue has been resolved in version 6.5.3 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This is halfway between a bug and a feature request, because I know TS 5 isn't supported yet, but figure it will be soon.
Current behavior
In a create-react-scripts application using TypeScript v5, the following messages occur at compile time:
and
Expected behavior
No TypeError upon compilation.
Steps to reproduce the issue
Build a create-react-app application with the typescript template In
package.json
: Set the version of the typescript package to5.0.0-beta
Inpackage.json
: Add the following overrides section:Run
npm install --legacy-peer-deps
Runnpm run build
Environment