- This topic has 2 replies, 2 voices, and was last updated 4 years, 2 months ago by
jbeard.
-
AuthorPosts
-
jbeardParticipantI am working on an Angular project, and have a weird issue that seems to be about the Terminal+ shell environment, somehow.
I’ve included my version output from npm, if that’s of interest:
$ npm version
{
‘fueland-info’: ‘0.0.0’,
npm: ‘6.14.12’,
ares: ‘1.16.1’,
brotli: ‘1.0.9’,
cldr: ‘37.0’,
icu: ‘67.1’,
llhttp: ‘2.1.3’,
modules: ’83’,
napi: ‘7’,
nghttp2: ‘1.41.0’,
node: ‘14.16.1’,
openssl: ‘1.1.1k’,
tz: ‘2020a’,
unicode: ‘13.0’,
uv: ‘1.40.0’,
v8: ‘8.4.371.19-node.18’,
zlib: ‘1.2.11’
}My issue is that the generated app acts differently when run within the eclipse/Terminal+ environment (whether using the start button, or just using ng serve in the command line), than the same app run in an actual bash terminal window.
If run in a standard terminal window, everything works as expected, but within the eclipse/Terminal+ environment, it’s as if some of the modules are not available (In this case, it acts as if BroserAnimationModule (Or NoopAnimationModule) are not present.
I’ve spent a couple days looking for a difference between the environments, and am a bit stumped.
I’m hoping someone there has some clue to give me on thisApril 20, 2021 at 10:02 am #673180
Salvador CabreraMemberHi jbeard,
Can you please let us know what version of angular and angular cli you are using?
Also, please try running the application usingSKIP_DISABLE_IVY=1 ng serve
and check if there is any difference.Cheers,
SalApril 21, 2021 at 8:50 am #673207
jbeardParticipantHi Sal,
Both environments report as follows:
—————————————
Angular CLI: 11.2.8
Node: 14.16.1
OS: linux x64Angular: 11.2.9
… animations, common, compiler, compiler-cli, core, forms
… language-service, platform-browser, platform-browser-dynamic
… router
Ivy Workspace: YesPackage Version
———————————————————
@angular-devkit/architect 0.1102.8
@angular-devkit/build-angular 0.1102.8
@angular-devkit/core 11.2.8
@angular-devkit/schematics 11.2.8
@angular/cdk 11.2.8
@angular/cli 11.2.8
@angular/material 11.2.8
@schematics/angular 11.2.8
@schematics/update 0.1102.8
rxjs 6.5.3
typescript 4.0.6I can report though that your suggestion to run with “SKIP_DISABLE_IVY=1 ng serve” does fix the problem in Terminal+ (without causing issues running in a regular terminal).
Thanks for that
-
AuthorPosts