-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
[Karma] Uncaught ReferenceError: sourceMapSupport is not defined #1046
Comments
Hey @KrakenTyio, thanks for opening this issue! |
Hi, when i switch to default its work almost correct, ofc almost bc i use in custom handler for svg loader, but yes when i turn off (comment) features in project which is needed this custom loaders, everethinks work correct i found in other threats like that there is issue with this source-map-support and new ts-node version so issue is only when is setting wrote in ts also will be nice set different tsconfig options for config ts file and different for builded project which will be tested |
I locked the version of ts-node to 10.2.1 and that helped |
@DmitryEfimenko How did you lock ts-node to 10.2.1? |
@elliottregan in the package.json in the devDependencies in the version for the ts-node, make sure there is no "devDependencies": {
"ts-node": "10.2.1"
} |
Is there any updates for this issue? |
I just tried with [email protected], and the issue still exists. We're stuck on [email protected] still... |
I started a discussion on the release notes for the version of ts-node that broke this. Hoping to get more traction with the issue. |
I've responded with a tiny, tested, working fix in TypeStrong/ts-node#1507 but no one has followed up. So the traction issue appears to be external to ts-node. |
downgrading ts-node to V9 worked for me |
Replacing this => "ts-node": "^10.7.0", Worked for me. |
I have this issue after migration to angular 12
dev build work correctly also production
but running karma test is problem
this is still reported and than stuct, browser is open but cannot continue bc. same issue is in console
karma.conf.js
angular.json
tsconfig.spec.json
tsconfig.json
The text was updated successfully, but these errors were encountered: