-
Notifications
You must be signed in to change notification settings - Fork 108
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
Failed build under TypeScript 4.5.2 #499
Comments
Yes, we have this problem as well, see issue linked above. |
typescript can't be updated bc of this issue it seems like: monounity/karma-typescript#499
* Pin TypeScript due to monounity/karma-typescript#499
Solution is to implement better Map check on line if (lodash.isMap(resolvedModules)) { // Typescript 2.2+ for new ModeAwareCache Some easy fix is to create primitive
and use it on the line like
|
I created my own scoped package with fix https://www.npmjs.com/package/@sedlak.r/karma-typescript/v/5.5.2-issue499fix.2
|
karma-typescript is not working with TS 4.5.4, thus downgraded to TS 4.4.4 until this will be fixed. See monounity/karma-typescript#499 for more details.
* refactor: upgrade deps, switch to lefthook, fix tests karma-typescript is not working with TS 4.5.4, thus downgraded to TS 4.4.4 until this will be fixed. See monounity/karma-typescript#499 for more details. * test: remove IE11 and Linux Chrome 48 from test matrix, as those are outdated browsers * test: transpile fetch-mock bundle to es5 syntax to make ancient browsers happy fetch-mock's client-legacy-bundle was throwing an exception during execution. * test: remove IE11 and non-chromium Edge browsers from test matrix as they are dead * test: make tests work for latest browsers * test: make tests work for latest browsers
Also bumps `karma-typescript` to latest to address monounity/karma-typescript#499.
Under TypeScript 4.5.2, my tests fail to start with errors like:
The crux of this problem appears to happen at this line of compiler.ts:
Under TypeScript 4.4.4, the
resolvedModules
property of sourceFile is a true ES6 Map, as far as I can tell.Under TypeScript 4.5.2, that property has changed to the Map-like ModeAwareCache, which apparently isn't enough like a Map to satisfy whatever comes after this line.
Reverting to TypeScript 4.4 is a workaround.
The text was updated successfully, but these errors were encountered: