In Angular, on making an observable, error "Object is possibly null" appears, but it is not null

Question

I have two projects, and in one, this code yields no error:

  form: FormGroup = new FormGroup({
    s: new FormControl('')
  })

  fo$ = this.form.get('s').valueChanges.pipe(
    map(a => console.log('something'))
  );

But in my new project, this brings up the error "Object is possibly 'null'." How can I solve this?

https://stackoverflow.com/questions/40349987/how-to-suppress-error-ts2533-object-is-possibly-null-or-undefined — Berk Kurkcuoglu, Jun 10 '22 at 23:17

NeNaD · Accepted Answer · 2022-06-10T23:35:16.820

1

Problem

It's probably the case where you have strict mode enabled in one project, and disabled in other project.

Solution

Go to the tsconfig.json file and disable strict mode in the project where it's enabled.

edited Jun 10 '22 at 23:35

answered Jun 10 '22 at 23:21

NeNaD

18,172
8
47
89

WHen I do the import { UntypedFormGroup, UntypedFormControl } from '@angular/forms'; I am getting error. These untypedformgroup and ubntypedformcontrol don't exist on my system. How to add (or install) them? – Vladimir Despotovic Jun 10 '22 at 23:25
1

Is your project created with Angular 14? – NeNaD Jun 10 '22 at 23:26
Angular is 13. Node is 14. – Vladimir Despotovic Jun 10 '22 at 23:27
1

Ok then... `UntypedFormGroup` and `UntypedFormControl` are introduced in Angular 14. Can you check `tsconfig.json` file and check if `strict` mode is enabled in one project, but disabled on other? – NeNaD Jun 10 '22 at 23:30
1

changing the strict to false solved the problem. – Vladimir Despotovic Jun 10 '22 at 23:32
Nice! I updated my answer with that info as a solution. – NeNaD Jun 10 '22 at 23:35

In Angular, on making an observable, error "Object is possibly null" appears, but it is not null

1 Answers1

Problem

Solution