Error in console: ng.probe is not a function

Question

Yesterday I updated Angular CLI and core to 8.0.0v. After that I successfully initialized a new app and ran it. Once the app was built and served on localhost:4200 I opened the console and there was an error:

ng.probe is not a function

I tried to research the issue, but there was no relevant info about it.

Actual result:

After ng serve / npm start there is an issue in the console:

Uncaught TypeError: ng.probe is not a function. Current console state Current angular state

Expected result:

No error in the console

Yes it was set by default after ng new. Even more i debug my main.ts file to check envoirment and it was set to dev — Andon Mitev, May 30 '19 at 06:51

Eli · Answer 1 · 2020-07-01T11:54:29.770

48

If someone is looking for an alternative to:

ng.probe($0)

In Ivy, then please try this:

 ng.getComponent($0);

Found it here, https://juristr.com/blog/2019/09/debugging-angular-ivy-console/

Thought I'd add this here for completion.

Note about ng.getComponent: you must focus the component tag ( e.g. <app-my-component> ) in the developer tools elements so that it will be in $0. It doesn't search up the hierarchy for parent components ( like ng.probe does ).

edited Jul 01 '20 at 11:54

answered Mar 05 '20 at 06:51

Eli

1,670
1
20
23

1

You can also save component instances in global variables and then use ng.getComponents(). Details are discussed here https://mobiarch.wordpress.com/2020/07/08/ng-probe-no-more/ – RajV Jul 08 '20 at 17:28

MrMalith · Answer 2 · 2021-03-01T07:08:53.120

33

If you're using Augury extension, disable or remove it. then, check the console. I've had the same issue and I removed the Augury.

Augury is having different set of debugging APIs, that's why that error occur.

edited Mar 01 '21 at 07:08

answered Apr 27 '20 at 18:02

MrMalith

1,352
14
22

2

this is the cause of the problem – Duc Trung Mai Feb 01 '21 at 03:58
I removed mine and it's still doing it. – BBaysinger Feb 22 '21 at 13:08
Maybe you're having a different problem than mine. you can try different solutions in this post as well – MrMalith Mar 01 '21 at 07:10

score 17 · Answer 3 · answered Oct 03 '19 at 07:09

17

Yes, augury assumes angular dev mode is active if window.ng exists, but ivy doesn't export probe right now

I have augury but after I disable the extension there is no error anymore.

answered Oct 03 '19 at 07:09

Mrinal Jain

773
9
21

Thanks! Can confirm, turning off Augury chrome extension removed that console error for me as well. – aonepathan Nov 17 '19 at 13:25
I can confirm also that the same problems happens with firefox. A removing the extensión solved it. :) – Juan Antonio Sep 16 '20 at 08:13
What is irritating is, that Augury does work for chrome by now. It just does not for Firefox. – Philipp Doerner Dec 13 '20 at 12:12

score 7 · Answer 4 · edited Apr 22 '22 at 09:04

7

You could also run without Ivy with this in your tsconfig.app.json

"angularCompilerOptions": { "enableIvy": false }

edited Apr 22 '22 at 09:04

BuZZ-dEE

6,075
12
66
96

answered Mar 17 '20 at 14:06

Mr T

81
1
4

score 2 · Answer 5 · answered Jun 06 '21 at 04:37

This is not exactly related to this question, but googling led me here. So, I am leaving the solution to my problem here in hopes that it will help others who face the same problem.

I was getting ng.probe not a function error when I created a angular project using dotnet sdk(version 5.0.300) and ran it locally. The project was using @angular/core v8.2.12, and @angular/cli v8.3.29.

I was able to solve the problem by update these packages using -

ng update @angular/core@8 @angular/cli@8

or

npm run ng update @angular/core@8 @angular/cli@8

Error in console: ng.probe is not a function

5 Answers5

Linked