Production build fails after upgrading to ionic 2.1.0 #236

vbolshutkin · 2017-03-10T17:03:18Z

In clean working copy cloned from master branch with re-installed npm dependencies running ionic build browser --prod fails with the following error:

[19:01:01]  ngc started ... 
[19:01:02]  build prod failed: Error encountered resolving symbol values statically. Calling function 
            'NoOpAnimationDriver', function calls are not supported. Consider replacing the function or lambda with a 
            reference to an exported function, resolving symbol AnimationDriver.NOOP in 
            /home/user/devel/clicker/node_modules/@angular/platform-browser/src/dom/animation_driver.d.ts,
            resolving symbol BrowserTestingModule in 
            /home/user/devel/clicker/node_modules/@angular/platform-browser/testing/browser.d.ts, 
            resolving symbol BrowserTestingModule in 
            /home/user/devel/clicker/node_modules/@angular/platform-browser/testing/browser.d.ts 
[19:01:02]  ionic-app-script task: "build" 
[19:01:02]  Error: Error encountered resolving symbol values statically. Calling function 'NoOpAnimationDriver', 
            function calls are not supported. Consider replacing the function or lambda with a reference to an exported 
            function, resolving symbol AnimationDriver.NOOP in 
            /home/user/devel/clicker/node_modules/@angular/platform-browser/src/dom/animation_driver.d.ts,
            resolving symbol BrowserTestingModule in 
            /home/user/devel/clicker/node_modules/@angular/platform-browser/testing/browser.d.ts, 
            resolving symbol BrowserTestingModule in 
            /home/user/devel/clicker/node_modules/@angular/platform-browser/testing/browser.d.ts 
Error: Error encountered resolving symbol values statically. Calling function 'NoOpAnimationDriver', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AnimationDriver.NOOP in /home/user/devel/clicker/node_modules/@angular/platform-browser/src/dom/animation_driver.d.ts, resolving symbol BrowserTestingModule in /home/user/devel/clicker/node_modules/@angular/platform-browser/testing/browser.d.ts, resolving symbol BrowserTestingModule in /home/user/devel/clicker/node_modules/@angular/platform-browser/testing/browser.d.ts
    at simplifyInContext (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:25703:25)
    at StaticReflector.simplify (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:25715:15)
    at StaticReflector.annotations (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:25213:62)
    at NgModuleResolver.resolve (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:17573:84)
    at CompileMetadataResolver.getNgModuleMetadata (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:18081:62)
    at CompileMetadataResolver.getNgModuleSummary (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:18037:54)
    at /home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:18127:70
    at Array.forEach (native)
    at CompileMetadataResolver.getNgModuleMetadata (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:18122:51)
    at addNgModule (/home/user/devel/clicker/node_modules/@angular/compiler/bundles/compiler.umd.js:24975:60)

Before upgrading to ionic 2.1.0 (commit 13a6cd6) it worked well.

The text was updated successfully, but these errors were encountered:

lathonez · 2017-03-11T00:30:44Z

The only thing I can think of is the angular upgrade causing it? Try downgrading to angular2.1 to see if it solves? Not a solution but I am AFK this weekend and it gets you somewhere.

…

On Sat, 11 Mar 2017 at 03:33, Vladimir Bolshutkin ***@***.***> wrote: In clean working copy cloned from master branch with re-installed npm dependencies running ionic build browser --prod fails with the following error: [19:01:01] ngc started ... [19:01:02] build prod failed: Error encountered resolving symbol values statically. Calling function 'NoOpAnimationDriver', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AnimationDriver.NOOP in ***@***.***/platform-browser/src/dom/animation_driver.d.ts, resolving symbol BrowserTestingModule in ***@***.***/platform-browser/testing/browser.d.ts, resolving symbol BrowserTestingModule in ***@***.***/platform-browser/testing/browser.d.ts [19:01:02] ionic-app-script task: "build" [19:01:02] Error: Error encountered resolving symbol values statically. Calling function 'NoOpAnimationDriver', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AnimationDriver.NOOP in ***@***.***/platform-browser/src/dom/animation_driver.d.ts, resolving symbol BrowserTestingModule in ***@***.***/platform-browser/testing/browser.d.ts, resolving symbol BrowserTestingModule in ***@***.***/platform-browser/testing/browser.d.ts Error: Error encountered resolving symbol values statically. Calling function 'NoOpAnimationDriver', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AnimationDriver.NOOP in ***@***.***/platform-browser/src/dom/animation_driver.d.ts, resolving symbol BrowserTestingModule in ***@***.***/platform-browser/testing/browser.d.ts, resolving symbol BrowserTestingModule in ***@***.***/platform-browser/testing/browser.d.ts at simplifyInContext ***@***.***/compiler/bundles/compiler.umd.js:25703:25) at StaticReflector.simplify ***@***.***/compiler/bundles/compiler.umd.js:25715:15) at StaticReflector.annotations ***@***.***/compiler/bundles/compiler.umd.js:25213:62) at NgModuleResolver.resolve ***@***.***/compiler/bundles/compiler.umd.js:17573:84) at CompileMetadataResolver.getNgModuleMetadata ***@***.***/compiler/bundles/compiler.umd.js:18081:62) at CompileMetadataResolver.getNgModuleSummary ***@***.***/compiler/bundles/compiler.umd.js:18037:54) at ***@***.***/compiler/bundles/compiler.umd.js:18127:70 at Array.forEach (native) at CompileMetadataResolver.getNgModuleMetadata ***@***.***/compiler/bundles/compiler.umd.js:18122:51) at addNgModule ***@***.***/compiler/bundles/compiler.umd.js:24975:60) Before upgrading to ionic 2.1.0 (commit 13a6cd6 <13a6cd6>) it worked well. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#236>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG5tSBGY27YP9qnIsp-kHmk7RZ66xepUks5rkYJXgaJpZM4MZoDz> .

lathonez · 2017-03-13T03:47:24Z

replicated

lathonez · 2017-03-13T03:58:24Z

confirmed that downgrading to angular 2.2.1 fixes (this specific problem) - not a solution

lathonez · 2017-03-13T04:01:11Z

fair few hits in angular/cli:

Suggestion seems to be excluding test.ts from build

lathonez · 2017-03-14T01:20:54Z

Straight upgrade of Ionic to angular2.4 on a starter project does not give the error, suggesting something from the testing framework must be the root cause (as suggested above)

saschwarz · 2017-03-14T01:50:42Z

I fixed this in my project by adding the following to: tsconfig.json:

"exclude": [
"src/test.ts",
"node_modules",
"**/*.spec.ts"
],

See also: ionic-team/ionic-app-scripts#806

lathonez · 2017-03-14T01:55:14Z

@saschwarz thanks - confirmed working here, needed both test.ts and *.spec.ts. There was a reason we didn't do this..

lathonez · 2017-03-14T01:59:14Z

Reason: #174 (comment)

Excluding spec makes the testing imports go missing in the editor. I do hate the fact that when I change code (and my tests break), ionic serve stops working though.

Maybe exlcuding spec from the main tsconfig.json is the lesser of two evils?

Also presumably there's a way of configuring one's editor outside of the project's tsconfig.json

lathonez · 2017-03-14T02:28:41Z

above should sort it, added some tests for the browser build into CI as a quick win.

TODO - update blog if this is legit

kamok · 2017-04-18T15:37:51Z

This issue came up again after upgrading to Ionic 3. The cause is a d.ts file related to @ionic/cloud-angular which I had installed previously to test out their service. After removing it, rolling back all the steps here: https://docs.ionic.io/setup.html, I was able to build again. I don't know why excluding node_modules in ts.config.json doesn't work. But that was where the file was.

lathonez · 2017-04-18T21:32:07Z

Not happening here or on travis:

https://s3.amazonaws.com/archive.travis-ci.org/jobs/220910203/log.txt

I've never used cloud-angular so I guess isolated to that.

lathonez added a commit that referenced this issue Mar 14, 2017

Reinstate tsconfig.json excludes for ionic build --prod addressing #236

f75ec74

lathonez closed this as completed Mar 14, 2017

lathonez mentioned this issue Oct 13, 2017

Different tsconfig.json for ionic? #273

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Production build fails after upgrading to ionic 2.1.0 #236

Production build fails after upgrading to ionic 2.1.0 #236

vbolshutkin commented Mar 10, 2017

lathonez commented Mar 11, 2017 via email

lathonez commented Mar 13, 2017

lathonez commented Mar 13, 2017

lathonez commented Mar 13, 2017

lathonez commented Mar 14, 2017

saschwarz commented Mar 14, 2017 •

edited

Loading

lathonez commented Mar 14, 2017

lathonez commented Mar 14, 2017 •

edited

Loading

lathonez commented Mar 14, 2017

kamok commented Apr 18, 2017 •

edited

Loading

lathonez commented Apr 18, 2017

Production build fails after upgrading to ionic 2.1.0 #236

Production build fails after upgrading to ionic 2.1.0 #236

Comments

vbolshutkin commented Mar 10, 2017

lathonez commented Mar 11, 2017 via email

lathonez commented Mar 13, 2017

lathonez commented Mar 13, 2017

lathonez commented Mar 13, 2017

lathonez commented Mar 14, 2017

saschwarz commented Mar 14, 2017 • edited Loading

lathonez commented Mar 14, 2017

lathonez commented Mar 14, 2017 • edited Loading

lathonez commented Mar 14, 2017

kamok commented Apr 18, 2017 • edited Loading

lathonez commented Apr 18, 2017

saschwarz commented Mar 14, 2017 •

edited

Loading

lathonez commented Mar 14, 2017 •

edited

Loading

kamok commented Apr 18, 2017 •

edited

Loading