question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItΒ collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot use 'in' operator to search for 'base10Value' in null

See original GitHub issue

🐞 bug report

`npm start

utsource-wap@0.0.0 start E:\Wap-Angular ng serve --port 8001

Compiling @angular/animations : module as esm5 Compiling @angular/compiler/testing : module as esm5 Compiling @angular/core : module as esm5 Error: Error on worker #1: TypeError: Cannot use β€˜in’ operator to search for β€˜base10Value’ in null at Object.createLiteral (E:\Wap-Angular\node_modules\typescript\lib\typescript.js:66137:56) at TypeTranslatorVisitor.visitLiteralExpr (E:\Wap-Angular\node_modules@angular\compiler-cli\src\ngtsc\translator\src\translator.js:406:48) at LiteralExpr.visitExpression (E:\Angular\node_modules@angular\compiler\bundles\compiler.umd.js:1554:28) at TypeTranslatorVisitor.translateExpression (E:\Angular\node_modules@angular\compiler-cli\src\ngtsc\translator\src\translator.js:490:33) at E:\Angular\node_modules@angular\compiler-cli\src\ngtsc\translator\src\translator.js:448:73 at Array.map (<anonymous>) at TypeTranslatorVisitor.visitLiteralArrayExpr (E:\Angular\node_modules@angular\compiler-cli\src\ngtsc\translator\src\translator.js:448:38) at LiteralArrayExpr.visitExpression (E:\Angular\node_modules@angular\compiler\bundles\compiler.umd.js:1850:28) at TypeTranslatorVisitor.translateExpression (E:\Angular\node_modules@angular\compiler-cli\src\ngtsc\translator\src\translator.js:490:33) at TypeTranslatorVisitor.visitExpressionType (E:\Angular\node_modules@angular\compiler-cli\src\ngtsc\translator\src\translator.js:357:33) at ClusterMaster.onWorkerMessage (E:\Angular\node_modules@angular\compiler-cli\ngcc\src\execution\cluster\master.js:165:27) at E:\Angular\node_modules@angular\compiler-cli\ngcc\src\execution\cluster\master.js:49:95 at ClusterMaster.<anonymous> (E:\Wap-Angular\node_modules@angular\compiler-cli\ngcc\src\execution\cluster\master.js:245:57) at step (E:\Angular\node_modules\tslib\tslib.js:139:27) at Object.next (E:\Angular\node_modules\tslib\tslib.js:120:57) at E:\Angular\node_modules\tslib\tslib.js:113:75 at new Promise (<anonymous>) at Object.__awaiter (E:\Angular\node_modules\tslib\tslib.js:109:16) at EventEmitter.<anonymous> (E:\Angular\node_modules@angular\compiler-cli\ngcc\src\execution\cluster\master.js:239:32) at EventEmitter.emit (events.js:223:5) An unhandled exception occurred: NGCC failed.`

Affected Package

The issue is caused by package @angular/....

Is this a regression?

Yes, the previous version in which this bug was not present was: ....

Description

A clear and concise description of the problem...

πŸ”¬ Minimal Reproduction

https://stackblitz.com/...

πŸ”₯ Exception or Error





🌍 Your Environment

Angular CLI: 9.1.0 Node: 12.14.1 OS: win32 x64

Angular: 9.1.0 … animations, cli, common, compiler, core, forms … language-service, localize, platform-browser … platform-browser-dynamic, platform-server, router Ivy Workspace: Yes

Package Version

@angular-devkit/architect 0.901.0 @angular-devkit/build-angular 0.901.0 @angular-devkit/build-optimizer 0.901.0 @angular-devkit/build-webpack 0.901.0 @angular-devkit/core 9.1.0 @angular-devkit/schematics 9.1.0 @angular/compiler-cli 9.0.7 @ngtools/webpack 9.1.0 @nguniversal/builders 9.0.2 @nguniversal/common 9.0.2 @nguniversal/express-engine 9.0.2 @schematics/angular 9.1.0 @schematics/update 0.901.0 rxjs 6.5.4 typescript 3.7.5 webpack 4.42.0 Angular Version:





Anything else relevant?

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

14reactions
JoostKcommented, Mar 26, 2020

Hello @yangjunfocus,

I know this error, as I experienced it while implementing a new feature in the compiler. I fixed this scenario in @angular/compiler-cli 9.1.0 but you are still on 9.0.7. This results in an incompatibility between @angular/compiler at version 9.1.0.

Please upgrade @angular/compiler-cli to 9.1.0 to fix the problem.

0reactions
angular-automatic-lock-bot[bot]commented, May 1, 2020

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Angular 2 Routing ERROR in Cannot use "in" operator to ...
I receive the following Error: ERROR in Cannot use "in" operator to search for "providers" in null. My providers section is empty because...
Read more >
TypeError: cannot use 'in' operator to search for 'x' in 'y'
The in operator can only be used to check if a property is in an object. ... const foo = null; "bar" in...
Read more >
JavaScript TypeError - Cannot use 'in' operator to search for 'X ...
This JavaScript exception Cannot use 'in' operator to search for 'X' in 'Y' occurs if in operator is used to search in strings,...
Read more >
cannot use 'in' operator to search for vue
... typeerror: cannot use 'in' operator to search for 'validatestatus' in axios, error in cannot use 'in' operator to search for 'base 10...
Read more >
Javascript Basic Flashcards - Quizlet
Parse a string to base 10 value ... null undefined composite data type - object ... ______ operator can be used to find...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found