2.1.0 AOT error
See original GitHub issueBuilding my app with angular-cli and ng-bootstrap 2.1.0 yields
ERROR in ./node_modules/@ng-bootstrap/ng-bootstrap/datepicker/datepicker.module.js
Module not found: Error: Can't resolve './ngb-date-adapter' in 'myproject/node_modules/@ng-bootstrap/ng-bootstrap/datepicker'
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:19 (3 by maintainers)
Top Results From Across the Web
PH43608: LOADING DATA FROM ONE AOT TO ANOTHER ...
Error description. When load data from AOT in IDAA V5 to another AOT in IDAA V7 by IDAA Loader, it corrupts many (...
Read more >building a project including mdb pro for production with AoT
When building an angular 6 project including MDB Pro 6.1.1 downloaded through the zip and installed in the project as per the downloaded...
Read more >Error: Cannot find module when using ng serve --aot
I migrated my angular project from 6 to 7, I'm using lazy loading mechanism to load the modules. But when i'm taking the...
Read more >Release Notes 2.1 | Photon Engine
2.1.0. Breaking Changes. Unity: Editor code has been refactored and, to simplify future updates, some files have been merged. That means that any...
Read more >ng build is failing for ADF 2.1.0 - Alfresco Hub
Hi, I am getting following error when I am trying to create prod build. Build is working fine with development target. Is this...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey guys, I’m having the same issue on ng-bootstrap v3.2.
I’m getting module not found error in all of ng-bootstrap module (accordion, alert, typeahead, etc.) I’ve tried deleting my node_modules folder and clearing npm cache but the problem persist.
Am I the only one having this problem?
I completely removed my node_modules folder and reinstalled everything…no errors this time at all. All is well. Thanks!