Can't bind to 'ngModel' since it isn't a known property of 'input'
Asked Answered
I

51

2127

I have this simple input in my component which uses [(ngModel)] :

<input type="text" [(ngModel)]="test" placeholder="foo" />

And I get the following error when I launch my app, even if the component is not displayed.

zone.js:461 Unhandled Promise rejection: Template parse errors: Can't bind to 'ngModel' since it isn't a known property of 'input'.

Here is the component.ts:

import { Component, EventEmitter, Input, OnInit, Output } from '@angular/core';
import { Intervention } from '../../model/intervention';

@Component({
   selector: 'intervention-details',
   templateUrl: 'app/intervention/details/intervention.details.html',
   styleUrls: ['app/intervention/details/intervention.details.css']
})
    
export class InterventionDetails
{
   @Input() intervention: Intervention;
    
   public test : string = "toto";
}
Invocate answered 11/8, 2016 at 9:44 Comment(8)
I'm having the same problem since they updated to rc5 yesterday (interestingly it works for my colleague..) I think @abreneliere is talking about their tutorials - angular.io/docs/ts/latest/tutorialWobble
Yes I referred to the Tour of heroes tutorial because it does use a ngModel.Heavily
I'm just staring Angular and saw this error when doing the Tour of Heroes tutorial. Sure enough, they now call this out in the very next line and tell you how/why to correct it.Service
It uses the same fix for textarea tooSmallclothes
For what it's worth, I encountered this error in IONIC-4 ( 4.11.0 ) when working with Forms Validation. If I do nothing else except add formControlName="myControl" to any <ion-input> anywhere in the form, I get the ngModel binding error message. Alternate properties, like formControlName1="myControl" do not cause this error.Chemurgy
If you get that error message only when running tests, see the related question angular2 testing: Can't bind to 'ngModel' since it isn't a known property of 'input'Bruno
This error can also be caused by not importing the module that's attempting to use ngModel into appModule. Say you have secondModule, and thirdModule and you import only secondModule into appModule and you import thirdModule into secondModule and then thirdModule trys to use ngModel, you'll get this error until you import thirdModule into appModule.Ima
Everyone says that you need the FormsModule in app.module.ts file. I only have one module and it is defined in there but I get the same message. If I remove the ngModel from the input statement it works fine. I am on Angular 12 - has that changed?Apices
I
2883

Yes, that's it. In the app.module.ts file, I just added:

import { FormsModule } from '@angular/forms';

[...]

@NgModule({
  imports: [
    [...]
    FormsModule
  ],
  [...]
})
Invocate answered 11/8, 2016 at 12:30 Comment(11)
Actually, I prefer this Answer to Gabriele's (which is just a link). Here, the exact code is presented. Annoyingly, I hit this problem just following John Paps's "Introduction to Angular 2" on PluralSight, and this issue wasn't even mentioned. For them, the 2-way binding just worked.Host
This worked, but only after I imported it into my sub-module. It's not completely clear to beginners that this doesn't get inherited by sub-modules.Mell
In my case, My use of braces were wrong. I was using [{ngModel}] instead of the correct one: [(ngModel)]Subglacial
For those who find this because of a similar failure with Jasmine, you'll need to add these imports to the component.spec.ts file as well.Ladybug
And for where to put it (regarding the Jasmine error): #39585034Horus
This error does also happen in tests. If that is your problem, you also have to import the FormsModule into your TestBed, similar to Anthonys solution: TestBed.configureTestingModule({ declarations: […Component], imports: [ FormsModule ] })Unknow
@Mell because as you may know the FormsModule is used in the component, right? and components have local scope, not global one. that's why you need to imported it there. There are some modules (such as services) that have global scope which don't need to be imported to every nested component's module.Underlay
@Subglacial remember "banana in a box": [()] not mustaches in a box [{}]...gross! angular.io/guide/template-syntaxSurvance
The FormModule import must be added into the module where you are trying to use the directive ngModel.Plasterwork
I am happy to announce this solution is covered by Assistant medium.com/@tomaszs2/…Majorette
I didn't knew that [(ngModel)] is case sensitive, I wasted a lot of time, done everything and in the end it came out that I was using [(ngmodel)] all in smallParavane
F
680

In order to be able to use two-way data binding for form inputs you need to import the FormsModule package in your Angular module.

For more information, see the Angular 2 official tutorial here and the official documentation for forms.

Factor answered 11/8, 2016 at 10:58 Comment(6)
I have to admit that I start with Angular on Monday (so 4 days ago) and was doing their tutorials so I'm pretty sure I did something wrong but for me importing FormsModule didn't work. Then I added import { FORM_DIRECTIVES } from '@angular/forms'; and added the FORM_DIRECTIVES to directives and yeah my binding is working again (to be clear it was working before rc5 release)Wobble
Which seems to be related to this #31624379Wobble
@Wobble the issue you're having with the tutorial is that on August 7th, when you started, the tutorials were running Release Candidate 4. As of August 8th, they are at Release Candidate 5, which has different syntaxStalemate
Imported angular Forms along with FORM_DIRECTIVES saved me.. :)Holler
FORM_DIRECTIVES are dead just in caseEnnoble
It's worth nothing that, if you are using a SharedModule, you might need to import FormsModule there aswell.Diaphony
M
306

For using [(ngModel)] in Angular 2, 4 & 5+, you need to import FormsModule from Angular form...

Also, it is in this path under forms in the Angular repository on GitHub:

angular / packages / forms / src / directives / ng_model.ts

Probably this is not a very pleasurable for the AngularJS developers as you could use ng-model everywhere anytime before, but as Angular tries to separate modules to use whatever you'd like you to want to use at the time, ngModel is in FormsModule now.

Also, if you are using ReactiveFormsModule it needs to import it too.

So simply look for app.module.ts and make sure you have FormsModule imported in...

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';  // <<<< import it here
import { AppComponent } from './app.component';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule, FormsModule // <<<< And here
  ],
  providers: [],
  bootstrap: [AppComponent]
})

export class AppModule { }

Also, these are the current starting comments for Angular4 ngModel in FormsModule:

/**
 * `ngModel` forces an additional change detection run when its inputs change:
 * E.g.:
 * ```
 * <div>{{myModel.valid}}</div>
 * <input [(ngModel)]="myValue" #myModel="ngModel">
 * ```
 * I.e. `ngModel` can export itself on the element and then be used in the template.
 * Normally, this would result in expressions before the `input` that use the exported directive
 * to have and old value as they have been
 * dirty checked before. As this is a very common case for `ngModel`, we added this second change
 * detection run.
 *
 * Notes:
 * - this is just one extra run no matter how many `ngModel` have been changed.
 * - this is a general problem when using `exportAs` for directives!
 */

If you'd like to use your input, not in a form, you can use it with ngModelOptions and make standalone true...

[ngModelOptions]="{standalone: true}"

For more information, look at ng_model in the Angular section here.

Merger answered 10/10, 2017 at 12:46 Comment(0)
S
136

You need to import the FormsModule.

Open app.module.ts and add the lines

import { FormsModule } from '@angular/forms';

and

@NgModule({
    imports: [
       FormsModule
    ],
})
Solifidian answered 6/10, 2018 at 4:59 Comment(1)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
N
114

To resolve We must include FormModule in the app.module.ts file to avoid the Can't bind to ngModel as it isn't a known property of the input problem in Angular apps.

The steps are as follows,

Open app.module.ts and add the import line

import { FormsModule } from '@angular/forms';

and add FormsModule to imports

@NgModule({
    imports: [
       FormsModule
    ],
})

Figure 1.0 (app.module.ts file)

enter image description here

Nectar answered 25/4, 2021 at 18:2 Comment(3)
100% requires the FormsModule to be imported. Fixed the Issue for me.Lynettelynn
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
Importing the Mocked version is enough: MockModule(FormsModule)Hausmann
G
71

Assuming you have created a new NgModule, say AuthModule dedicated to handling your authentication needs, make sure to import FormsModule in that AuthModule too.

If you'll be using the FormsModule only in the AuthModule then you wouldn't need to import the FormModule in the default AppModule.

So something like this in the AuthModule:

import { NgModule }      from '@angular/core';
import { FormsModule } from '@angular/forms';

import { authRouting } from './auth.routing';
import { LoginComponent, SignupComponent } from './auth.component';

@NgModule({
  imports:      [
    authRouting,
    FormsModule
   ],
  declarations: [
    SignupComponent,
    LoginComponent
  ]
})
export class AuthModule { }

Then forget about importing in AppModule if you don't use the FormsModule anywhere else.

Gae answered 24/9, 2016 at 13:6 Comment(1)
I needed it at sub-module where I was using the Form features. Higher up the hierarchy was not sufficient.Abolish
A
53

Simple solution: In file app.module.ts -

Example 1

import {FormsModule} from "@angular/forms";
// Add in imports

imports: [
 BrowserModule,
 FormsModule
 ],

Example 2

If you want to use [(ngModel)] then you have to import FormsModule in app.module.ts:

import { FormsModule  } from "@angular/forms";
@NgModule({
  declarations: [
    AppComponent, videoComponent, tagDirective,
  ],
  imports: [
    BrowserModule,  FormsModule

  ],
  providers: [ApiServices],
  bootstrap: [AppComponent]
})
export class AppModule { }
Alberta answered 25/1, 2018 at 11:9 Comment(3)
Where exactly is the difference in the two examples?Olatha
in my case, had to import FormsModule on my component.module.tsLindsley
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
S
53

Import the FormsModule in those modules where you want to use the [(ngModel)]

enter image description here

Sultanate answered 3/12, 2019 at 11:49 Comment(4)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
@MartinSchneider then how its having this upvotes :)Sultanate
My guess: the default design by SO that shows more recent and trending answers above older ones and the fact that most users are lazy ;)Helmsman
is this works? if yes then close the topic :) @MartinSchneiderSultanate
P
51

There are two steps you need to follow to get rid of this error:

  1. import FormsModule in your app module
  2. Pass it as value of imports in @NgModule decorator

Basically, file app.module.ts should look like below:

    import { NgModule }      from '@angular/core';
    import { BrowserModule } from '@angular/platform-browser';
    import { FormsModule }   from '@angular/forms';
    import { AppComponent }  from './app.component';
    import {AppChildComponent} from './appchild.component';
    @NgModule({
      imports:      [ BrowserModule,FormsModule ],
      declarations: [ AppComponent, AppChildComponent ],
      bootstrap:    [ AppComponent ]
    })
    export class AppModule { }
Pullulate answered 9/12, 2016 at 7:0 Comment(1)
Thank you! I'd not declared it in the imports section and it was driving me insane when I moved a component into a sub-module.Melba
V
50

Sometimes, even though we are already imported BrowserModule, FormsModule and other related modules, we still may get the same error.

Then I realized that we need to import them in order, which is missed in my case. So the order should be like BrowserModule, FormsModule, and ReactiveFormsModule.

As per my understanding, feature modules should follow the basic modules of Angular.

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { AppComponent } from './app.component';

@NgModule({
  imports: [
    BrowserModule,
    FormsModule,
    ReactiveFormsModule
  ],
  providers: [],
  declarations: [
    AppComponent
  ],
  bootstrap: [AppComponent]
})
export class AppModule {}
Vyborg answered 9/9, 2019 at 6:54 Comment(5)
You have ReactiveFormsModule in your imports array, but not in your imports. just saying.Eudosia
Is there a way to find out the order? i.e. If we have a few more modules to import, how do I confirm the sequence?Haulm
As per my understanding, Feature Modules should follow the Basic Modules of Angular. In case of Feature Modules sequence, we don't need to worry because our Error cause is not related to them.Vyborg
2021 reporting in, to mention that FormsModule must be imported after NgModule. This error will appear otherwise. This answer is the only one that mentions the importance of the order!O
You don't need ReactiveFormsModule when using template driven forms :-> Order irrelevant.Lulululuabourg
W
39

I am using Angular 7.

I have to import ReactiveFormsModule, because I am using the FormBuilder class to create a reactive form.

import {
  FormsModule,
  ReactiveFormsModule } from '@angular/forms';

@NgModule({
  imports: [
    CommonModule,
    FormsModule,
    ReactiveFormsModule
  ], declarations: []})
Waler answered 5/2, 2019 at 8:29 Comment(0)
M
36

You need to import FormsModule in your root module if this component is in the root i.e. app.module.ts

Kindly open app.module.ts

Import FormsModule from @angular/forms

Ex:

import { FormsModule } from '@angular/forms';

and

@NgModule({
imports: [
   FormsModule
],
})
Matronage answered 24/4, 2019 at 8:6 Comment(1)
A slight extension to PRao's answer.Myasthenia
H
33

Import FormsModule in you app module.

It would let your application run well.

import { NgModule }      from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import {ContactListCopmponent} from './contacts/contact-list.component';
import { FormsModule }   from '@angular/forms';

import { AppComponent }  from './app.component';

@NgModule({
  imports: [
    BrowserModule,
    FormsModule
  ],
  declarations: [
    AppComponent,ContactListCopmponent
  ],
  bootstrap: [ AppComponent ]
})
export class AppModule { }
Horst answered 25/12, 2016 at 9:43 Comment(0)
P
27

I'm using Angular 5.

In my case, I needed to import ReactiveFormsModule too.

File app.module.ts (or anymodule.module.ts):

import { FormsModule, ReactiveFormsModule } from '@angular/forms';

@NgModule({
  imports: [
    CommonModule,
    FormsModule,
    ReactiveFormsModule
  ],
Pasha answered 4/5, 2018 at 22:19 Comment(3)
ReactiveFormsModule is required when you need FormGroup, FormControl ,Validators etc. For using ngModel, you don't require ReactiveFormsModule.Catalyst
@AmitChigadani Adding ReactiveFormModule is the only thing that made the error go away in my case. I'm using Angular 7.Beat
Looks like the latest versions of Angular requires the ReactiveFormsModule to be imported for the ngModel to work. I was trained on Angular 7 and the same when I practiced it did not work, because I had the latest @angular/cli in my machine. After adding this ReactiveFormsModule, it worked perfectly.Forbore
H
23

If someone is still getting errors after applying the accepted solution, it could be possibly because you have a separate module file for the component in which you want to use the ngModel property in input tag. In that case, apply the accepted solution in the component's module.ts file as well.

Hargrave answered 11/5, 2017 at 11:18 Comment(1)
That was already mentioned in an answer from 2016Helmsman
M
23

I know this question is about Angular 2, but I am on Angular 4 and none of these answers helped.

In Angular 4 the syntax needs to be

[(ngModel)]
Marozik answered 4/8, 2017 at 5:49 Comment(0)
T
19

If you are still getting the error after importing FormsModule correctly then check in your terminal or (windows console) because your project is not compiling (because of another error that could be anything) and your solution has not been reflected in your browser!

In my case, my console had the following unrelated error:

Property 'retrieveGithubUser' does not exist on type 'ApiService'.

Transgression answered 26/7, 2017 at 16:50 Comment(2)
What is the action to be taken (after checking)? Please respond by editing your question, not here in comments (without "Edit:", "Update:", or similar).Myasthenia
Peter, you don't seem to comprehend my answer. When I say "could be anything" means that after checking the error, the universe of actions to be taken are unlimited. My answer has been upvoted 17 times, which means that many developers found my answer complete and there is no need for an edit.Transgression
S
18

Import FormModule in file app.module

import { FormsModule } from '@angular/forms'; [...] @NgModule({ imports: [ [...] FormsModule ], [...] })
Skylark answered 7/3, 2020 at 5:25 Comment(1)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
N
16

ngModel is coming from FormsModule. There are some cases when you can receive this kind of error:

  1. You didn't import the FormsModule into the import array of modules where your component is declared - the component in which the ngModel is used.
  2. You have import the FormsModule into one module which is inherited of another module. In this case you have two options:
  • let the FormsModule be imported into the import array from both modules:module1 and module2. As the rule: Importing a module does not provide access to its imported modules. (Imports are not inherited)

    Enter image description here

  • declare the FormsModule into the import and export arrays in module1 to be able to see it in model2 also

    Enter image description here

  1. (In some version I faced this problem) You have imported the FormsModule correctly, but the problem is on the input HTML tag. You must add the name tag attribute for the input, and the object bound name in [(ngModel)] must be the same as the name into the name attribute

    Enter image description here

Nominalism answered 13/11, 2018 at 16:20 Comment(0)
V
16

You need to import the FormsModule in app.module.ts and add the lines

 import { FormsModule } from '@angular/forms';
    @NgModule({
      imports: [
       
        FormsModule
      ]
    })

The ngModel directive declared in the FormsModule lets you bind controls in your template-driven form to properties in your data model. When you include the directive using the syntax for two-way data binding, [(ngModel)], Angular can track the value and user interaction of the control and keep the view synced with the model.

Vendetta answered 21/2, 2022 at 3:34 Comment(1)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
W
15

In the module you are willing to use ngModel you have to import FormsModule

import { FormsModule } from '@angular/forms';

@NgModule({
  imports: [
    FormsModule,
  ],

})
export class AbcModule { }
Webster answered 17/7, 2018 at 4:59 Comment(2)
I was missing this in my app.module.ts, thank you Malindu!Gasometer
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
A
14

In ngModule you need to import FormsModule, because ngModel is coming from FormsModule. Please modify your app.module.ts like the below code I have shared

import { FormsModule, ReactiveFormsModule } from '@angular/forms';
import { BrowserAnimationsModule } from '@angular/platform-browser/animations';

@NgModule({
    declarations: [
         AppComponent,
         HomeComponent
    ],
    imports: [
         BrowserModule,
         AppRoutingModule,
         FormsModule
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }
Arnica answered 21/6, 2019 at 5:0 Comment(1)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
R
13

I faced the same problem and the reason was that I was using ngModel in my MenuComponent. I imported my MenuComponent in app.module.ts, but I forgot to add it to declarations array.

Error

Declaring the MenuComponent solved my issue. I.e., as shown in the below image:

Solved issue

Rebuke answered 4/10, 2020 at 12:55 Comment(1)
That has been mentioned here alreadyHelmsman
P
11

For my scenario, I had to import both [CommonModule] and [FormsModule] to my module

import { NgModule } from '@angular/core' 
import { CommonModule } from '@angular/common'; 
import { FormsModule } from '@angular/forms'; 

import { MyComponent } from './mycomponent'

@NgModule({
    imports: [
        CommonModule,
        FormsModule
    ],
    declarations: [
        MyComponent 
    ]
 }) 
export class MyModule { }
Philologian answered 21/12, 2017 at 16:41 Comment(0)
G
11

ngModel should be imported from @angular/forms because it is the part of FormsModule. So I advice you to change your app.module.ts in something like this:

import { FormsModule } from '@angular/forms';

[...]

@NgModule({
  imports: [
    [...]
    FormsModule
  ],
  [...]
})
Galyak answered 25/6, 2020 at 13:38 Comment(2)
How is this different from previous answers?Myasthenia
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
U
11

You need to import the FormsModule.

#Open app.module.ts
#add the lines

import { FormsModule } from '@angular/forms';
and

@NgModule({
    imports: [
       FormsModule   <--------add this 
    ],
})


if you are using reactive form then also added  ReactiveFormsModule
Unexacting answered 19/3, 2021 at 11:20 Comment(2)
Unfortunately, this answer doesn't add much value to the chosen one.Wretch
@FrancescoColamonici or the other 17 answers with the exact same solution.Ima
V
10

Angular 14+ Using Standalone Component

Import the form component directly into your standalone component:

import { FormsModule, NgForm } from '@angular/forms';
import { NgFor } from "@angular/common";

@Component({
  selector: 'app-table-view',
  standalone: true,
  imports: [ 
    NgFor,
    FormsModule
    ],  
  templateUrl: './table-view.component.html',
  styleUrls: ['./table-view.component.css']
})
Variola answered 3/3, 2023 at 21:44 Comment(1)
Or not make the component standalone.Whitening
E
9

Sometimes you get this error when you try to use a component from a module, which is not shared, in a different module.

For example, you have 2 modules with module1.componentA.component.ts and module2.componentC.component.ts and you try to use the selector from module1.componentA.component.ts in a template inside module2 (e.g. <module1-componentA [someInputVariableInModule1]="variableFromHTTPRequestInModule2">), it will throw the error that the someInputVariableInModule1 is not available inside module1.componentA.component.ts - even though you have the @Input() someInputVariableInModule1 in the module1.componentA.

If this happens, you want to share the module1.componentA to be accessible in other modules. So if you share the module1.componentA inside a sharedModule, the module1.componentA will be usable inside other modules (outside from module1), and every module importing the sharedModule will be able to access the selector in their templates injecting the @Input() declared variable.

Eaddy answered 30/8, 2017 at 23:51 Comment(3)
I have this exact problem, and you say, you should share the module so you can use componentA in ComponentC. But.. How do I share the module1? Which is the sintax to "share a module"? I guessed exporting module1 and then importing it in the module2 was enough sharing, but still having this problemOrthopedic
So to answer myself, this is how you share a module angular-2-training-book.rangle.io/handout/modules/…Orthopedic
Hey sorry i didn't see your comment that fast :) Yes, this is how you can create a SharedModule and import your own modules there, which you want to use in multiple other modules. Then you import the SharedModule where you want to use the module which is imported in the shared one.Eaddy
I
9
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { AppComponent } from './app.component';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    FormsModule     
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule {}
Interim answered 11/10, 2017 at 3:56 Comment(2)
An explanation would be in order.Myasthenia
Furthermore this answer does not add any value over the answers from 2016: Answer #1, Answer #2Helmsman
P
8

This is for the folks who use plain JavaScript instead of Type Script. In addition to referencing the forms script file on top of the page like below:

<script src="node_modules/@angular/forms/bundles/forms.umd.js"></script>

You should also tell the the module loader to load the ng.forms.FormsModule. After making the changes my imports property of NgModule method looked like below:

imports: [ng.platformBrowser.BrowserModule, ng.forms.FormsModule],

Peppi answered 12/12, 2016 at 0:37 Comment(0)
P
7

I upgraded from RC1 to RC5 and received this error.

I completed my migration (introducing a new app.module.ts file, changing package.json to include new versions and missing modules, and finally changing my main.ts to boot accordingly, based on the Angular2 quick start example).

I did an npm update and then an npm outdated to confirm the versions installed were correct, still no luck.

I ended up completely wiping the node_modules folder and reinstalling with npm install - Voila! Problem solved.

Percuss answered 24/8, 2016 at 4:42 Comment(0)
C
7

Actually in most of the cases the FormsModule was already imported. So what you have to do is you have to make sure that

  1. Your component is properly added in the declarations array in app.module.ts file.
  2. You should verify that the binding was well spelled. The correct spelling is [(ngModel)]
Colloquial answered 4/3, 2021 at 0:37 Comment(0)
B
6

For me the issue was, I forgot to declare the component in the declarations array of the module.

@NgModule({
 declarations: [yourcomponentName]
})
Bittersweet answered 27/8, 2020 at 12:50 Comment(1)
That has been mentioned here alreadyHelmsman
K
5

When I first did the tutorial, main.ts looked slightly different from what it is now. It looks very similar, but note the differences (the top one is correct).

Correct:

import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
import { AppModule } from './app.module';

platformBrowserDynamic().bootstrapModule(AppModule);

Old tutorial code:

import { bootstrap }    from '@angular/platform-browser-dynamic';
import { AppComponent } from './app.component';
bootstrap(AppComponent);
Kootenay answered 12/8, 2016 at 2:52 Comment(0)
P
5

Combining all the possible solutions :

  1. Check if your typing it correctly. It should be "[(ngModel)]" with "M" capital.
  2. Check if you have import FormsModule in your TS file.If not, you can do it like this :

In app.module.ts, add these lines

import { FormsModule } from '@angular/forms';

@NgModule({
  declarations: [
  ],
  imports: [
    xyz,
    abc,
    FormsModule
  ],
})
Preachment answered 2/7, 2022 at 16:54 Comment(2)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3 and others.Helmsman
@MartinSchneider I've already mentioned on the top. I've compiled them for easier access and save some time :)Preachment
C
4

For any version from Angular 2, you need to import FormsModule in your app.module.ts file and it will fix the issue.

Canny answered 3/8, 2018 at 14:41 Comment(1)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
S
4

Recently I found that mistake happened not only in case when you forgot to import FormsModule in your module. In my case problem was in this code:

<input type="text" class="form-control" id="firstName"
                   formControlName="firstName" placeholder="Enter First Name"
                   value={{user.firstName}} [(ngModel)]="user.firstName">

I fix it with change formControlName -> name

<input type="text" class="form-control" id="firstName"
                   name="firstName" placeholder="Enter First Name"
                   value={{user.firstName}} [(ngModel)]="user.firstName">
Sampling answered 5/7, 2019 at 8:8 Comment(1)
Yes Nikita the "name" property is also required for the template-driven approach to forms. The name property is used by the angular form directive to assign validation errors, for example.Lulululuabourg
D
4

Though the answer solves the issue, I would like to provide a little more information on this topic as I have also undergone this issue when I started to work on Angular projects.

A beginner should understand that there are two main types of forms. They are Reactive forms and Template-driven forms. From Angular 2 onward, it is recommended to use Reactive forms for any kind of forms.

Reactive forms are more robust: they're more scalable, reusable, and testable. If forms are a key part of your application, or you're already using reactive patterns for building your application, use reactive forms.

Template-driven forms are useful for adding a simple form to an application, such as an email list signup form. They're easy to add to an application, but they don't scale as well as reactive forms. If you have very basic form requirements and logic that can be managed solely in the template, use template-driven forms.

Refer Angular documents for more details.

Coming to the question, [(ngModel)]="..." is basically a binding syntax. In order to use this in your component HTML page, you should import FormsModule in your NgModule (where your component is present). Now [(ngModel)] is used for a simple two-way binding or this is used in your form for any input HTML element.

On the other hand, to use reactive forms, import ReactiveFormsModule from the @angular/forms package and add it to your NgModule's imports array.

For example, if my component HTML content does not have [(ngmodel)] in any HTML element, then I don't need to import FormsModule.

In my below example, I have completely used Reactive Forms and hence I don't need to use FormsModule in my NgModule.

Create GroupsModule:

import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { GroupsRoutingModule, routedAccountComponents } from './groups-routing.module';
import { ReactiveFormsModule } from '@angular/forms';
import { SharedModule } from '../shared/shared.module';
import { ModalModule } from 'ngx-bootstrap';
@NgModule({
    declarations: [
        routedAccountComponents
    ],
    imports: [
        CommonModule,
        ReactiveFormsModule,
        GroupsRoutingModule,
        SharedModule,
        ModalModule.forRoot()
    ]
})
export class GroupsModule {
}

Create the routing module (separated to main the code and for readability):


import { NgModule } from '@angular/core';
import { Routes, RouterModule } from '@angular/router';
import { GroupsComponent } from './all/index.component';
import { CreateGroupComponent } from './create/index.component';

const routes: Routes = [
  {
    path: '',
    redirectTo: 'groups',
    pathMatch: 'full'
  },
  {
    path: 'groups',
    component: GroupsComponent
  }
];


@NgModule({
  imports: [RouterModule.forChild(routes)],
  exports: [RouterModule]
})
export class GroupsRoutingModule { }


export const routedAccountComponents = [
  GroupsComponent,
  CreateGroupComponent
];

CreateGroupComponent html code

<form [formGroup]="form" (ngSubmit)="onSubmit()">
        <label for="name">Group Name</label>
        <div class="form-group">
            <div class="form-line">
                <input type="text" formControlName="name" class="form-control">
            </div>
        </div>
    </form>

CreateGroupComponent ts file


import { Component, OnInit, Output, EventEmitter } from '@angular/core';
import { DialogResult } from 'src/app/shared/modal';
import { FormGroup, FormControl, AbstractControl } from '@angular/forms';
import { Subject } from 'rxjs';
import { ToastrService } from 'ngx-toastr';
import { validateAllFormFields } from 'src/app/services/validateAllFormFields';
import { HttpErrorResponse } from '@angular/common/http';
import { modelStateFormMapper } from 'src/app/services/shared/modelStateFormMapper';
import { GroupsService } from '../groups.service';
import { CreateGroup } from '../model/create-group.model';

@Component({
    selector: 'app-create-group',
    templateUrl: './index.component.html',
    providers: [LoadingService]
})

export class CreateGroupComponent implements OnInit {
    public form: FormGroup;
    public errors: string[] = [];
    private destroy: Subject<void> = new Subject<void>();

    constructor(
        private groupService: GroupsService,
        private toastr: ToastrService
    ) { }

    private buildForm(): FormGroup {
        return new FormGroup({
            name: new FormControl('', [Validators.maxLength(254)])
        });
    }

    private getModel(): CreateGroup {
        const formValue = this.form.value;
        return <CreateGroup>{
            name: formValue.name
        };
    }

    public control(name: string): AbstractControl {
        return this.form.get(name);
    }

    public ngOnInit() {
        this.form = this.buildForm();
    }


    public onSubmit(): void {

         if (this.form.valid) {
             // this.onSubmit();
             //do what you need to do
         }
    }
}

I hope this helps developers to understand as to why and when you need to use FormsModule.

Deport answered 23/1, 2020 at 15:58 Comment(0)
K
4

This error will happen too even if the FormsModule is imported directly or indirectly (from a shared module for example) in the feature module, if the imported component is not declared on declarations:

Enter image description here

I followed Deborah Kurata's Angular Routing course. While I added the imported component ProductEditInfoComponent on Angular Route's component property, I forgot to add ProductEditInfoComponent on declarations property.

Adding the ProductEditInfoComponent on the declarations property would solve the NG8002: Can't bind to 'ngModel' since it isn't a known property of 'input'. problem:

Enter image description here

Kyne answered 10/3, 2020 at 11:1 Comment(0)
M
4

Main reason of this error is you forget to import FormsModule in your app.module.ts.

But sometimes in big projects you may forget add your component in its module and confront this error.

Merrile answered 19/1, 2021 at 9:55 Comment(1)
That has been mentioned here alreadyHelmsman
K
3

I was getting the same error when running my Angular tests because FormsModule was not added in the specification file.

We need to add it in all specification files whereas for the application to run successfully we will add at one place in the app.module.ts file.

Kochi answered 21/11, 2019 at 7:14 Comment(0)
L
3

Make sure for the template-driven forms approach (https://angular.io/guide/forms), as has already been mentioned by @Nikita Sychou, you have decorated the input field with the "name" property, eg

<form>
   <input [(ngModel)]="form.email" name="email"></input>

and that the FormsModule has been imported in the associated @NgModule. Both are preconditions for avoiding the "Can't bind to ngModel" errors. If you still get styling errors in your IDE e.g. IntelliJ complaining about the ngModel directive just ignore them.. you are good to go :-)

Lulululuabourg answered 23/7, 2021 at 23:39 Comment(0)
L
1

In my case I was forgetting to add the component that uses the forms module tools in my app.module declarations. Without this the application's import scope will not recognize the component and will not be able to use it.

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
import { HomeComponent } from './components/home/home.component';
import { RouterModule, Routes } from '@angular/router';
import { ReactiveFormsModule, FormsModule } from '@angular/forms';
import { HttpClientModule } from '@angular/common/http';

const routes: Routes = [
  { path: '', component: HomeComponent },
];

@NgModule({
  declarations: [
    AppComponent,
    HomeComponent <-- component that implements forms module
  ],
  imports: [
    BrowserModule,
    AppRoutingModule,
    RouterModule.forRoot(routes),
    HttpClientModule,
    FormsModule,
    ReactiveFormsModule
 ],
 providers: [],
 bootstrap: [AppComponent]
})
export class AppModule { }
Lotson answered 13/11, 2023 at 18:16 Comment(0)
T
0

Note: Remember that the ngModel directive is defined as a part of Angular FormsModule and you need to include FormsModule in the imports: [...] section of the Angular module metadata, in which you want to use it.

Tahoe answered 24/7, 2020 at 9:34 Comment(1)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
F
0

import { FormsModule } from '@angular/forms';

@NgModule({
  imports: [

    FormsModule
  ],

})
Favoritism answered 29/9, 2020 at 6:19 Comment(1)
How is this different from previous answers?Myasthenia
D
0

I am using Angular 9 and I have a '<form' tag with the [formGroup] property. I also had an '<input' tag specifying a button, which caused the error on the [(ngModel)] part.

I resolved the error by just removing only that (ngModel) part.

Dobson answered 2/11, 2020 at 14:39 Comment(0)
O
0

Before you can use two way binding in Angular you need to import the FormsModule package into your module.

You do this by adding FormsModule to the imports array inside your module (e.g. app.module.ts) like this.

import { FormsModule } from '@angular/forms';

@NgModule({
  imports: [
    ...,
    FormsModule     <-------
  ],
  [...]
})
Overlie answered 1/3, 2021 at 20:4 Comment(1)
This answer adds no further value over the answers from 2016: Answer #1, Answer #2, Answer #3Helmsman
D
0

I was getting the same error even that I added FormsModule as described above. So just a simple restart was required to finish the job.

Decasyllabic answered 18/6, 2021 at 7:58 Comment(0)
R
0

Make sure [(ngModel)] is actually spelled 'ngModel' with Capital M.. I lost some minutes for not seeing this

Radu answered 6/5, 2022 at 18:20 Comment(1)
correct , I mistakenly used [(ng-model)] , i used [(ngModel)] and it work.Eklund
C
0

It's a famous error in Angular occurs in Angular when you are trying to use the "ngModel" directive on an "input" element, but the "ngModel" directive is not recognized as a property of the "input" element. The solution, is to import the "FormsModule" in your application and include it in the "imports" array of your module. like this:

import { FormsModule } from '@angular/forms';
@NgModule({
imports: [
FormsModule,
// other imports
],
// other properties
})
export class AppModule { }
Coacher answered 31/1, 2023 at 7:47 Comment(0)
B
0

If you tried everything above, and more and still cannot solve it, read this.

I spent a long time finding the solution these errors too! And they are showing up on almost all html.

If

  • you recently updated your angular version
  • and vs code (sometimes) gives an error popup angular extension might not work correctly because ngcc operation failed

The solution is: to update Angular Language Service extension to. That's it!

Other related solutions I have come along but didn't solve my problems will be listed below. Maybe you have a different problem:

  • adding CommonModule, or schemas: [ CUSTOM_ELEMENTS_SCHEMA ] in the component
  • adding BrowserModule, or checking errors in app.module.ts
  • checking "target" version in tsconfig.json

Happy coding!

Basically answered 17/1 at 7:44 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.