Version 2.0.0 not working with --aot
See original GitHub issueI build with ng build --prod --no-sourcemap --aot
Already did:
npm cache clean
,
npm install
,
removed node_modules
,
imported as:
`import { NvD3Module } from ‘ng2-nvd3’;
import ‘d3’; import ‘nvd3’;`
Still failing on build, except on ng build --no-sourcemap
Went back to my last working version 2.0.0-rc3
and won’t work too…
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Could not AOT the assembly Microsoft.Net.Http.Headers.dll
This appears to be an issue with the latest version of Microsoft.Net.Http.Headers package. Downgrading to version 2.0.0 worked around the problem for me....
Read more >Material 8 libraries not working with AOT mode - Stack Overflow
I am using MatSelect, MatChips and many other Mat libraries but none seem to work with AOT mode enabled. Dropdowns, MatChip inputs are...
Read more >building a project including mdb pro for production with AoT
I have made a clean install using npm and got it to compile without problems apart dependencies warnings : warning " >ng-uikit-pro-standard@6.1.1" has ......
Read more >Changelog | Newtonsoft Json | 2.0.2 - Unity - Manual
[2.0.0] - 2020-04-20 ... Updated dll to AOT compatible version to allow for IL2CPP compilation ... Added some sanity tests to catch issues...
Read more >PyTorch 2.0
AOTAutograd overloads PyTorch's autograd engine as a tracing autodiff for generating ahead-of-time backward ... Some of this work has not started yet.
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
Oh ! I think your problem is your version of @angular/cli. Here is the issue: https://github.com/angular/angular-cli/issues/7151
Could you run
npm run build:dev > output.log
and copy the content ofoutput.log
?