Repository navigation
Third party lib works unless I use --prod #2393
Description
- OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10 - Versions. Please run
ng --version. If there's nothing outputted, please run
in a Terminal:node --versionand paste the result here:
angular-cli: 1.0.0-beta.11-webpack.2
node: 4.4.7 - The log given by the failure. Normally this include a stack trace and some
more information.
Error: Uncaught (in promise): No value accessor for form control with name: 'startDate' - Mention any other details that might be useful.
I'm using a third party lib (ng2-datepicker) which works when I use ng-serve, and also works when i use ng build. But as soon as I build with --prod it stops working and I get this error. Pulling my hair out trying to solve the issue, any ideas?
Thanks.
Activity
alexsorokoletov commentedon Sep 28, 2016
@tomhackettishida we use ng2-typeahead, works just fine with prod
tomwanzek commentedon Sep 28, 2016
I had a similar experience, possibly with the same root cause?
I published a service to inject D3 as a service (d3-ng2-service) into Angular 2, while its written in TS to published package built exports two version of the transpiled JS (ES5 target/ES 6 module) and (ES6 target/ES6 module).
When importing the service into an angular-cli (beta 15) project, there is no issue, including with the
--prodflag.I locally experimented with using Rollup to provide a UMD bundle as on of the builts, for other module loaders.
The experience I had was essentially the same, when linking the 'experimental' local package version. While the error message differed in detail, it only created a runtime error with
--prod, no problem occurred in dev mode.filipesilva commentedon Oct 6, 2016
This was a bug we had in
webpack.2but was fixed forwebpack.3: #1662angular-automatic-lock-bot commentedon Sep 6, 2019
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.