Node 15 and Ionic for JHipster

[Matt Raible]

Hey all,

I’m trying to test a reactive oauth2 backend with Ionic for JHipster on the frontend.

When I try to create an Ionic4J app, it fails on npm install with the following error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ion...@0.0.1
npm ERR! Found: @fortawesome/angular-f...@0.7.0
npm ERR! node_modules/@fortawesome/angular-fontawesome
npm ERR! @fortawesome/angular-fontawesome@"0.7.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @fortawesome/angular-fontawesome@"^0.6.1" from ng-jh...@0.14.0
npm ERR! node_modules/ng-jhipster
npm ERR! ng-jhipster@"0.14.0" from the root project

If I change my package.json to use ng-jh...@0.16.0, I get a new error:

npm ERR! While resolving: ion...@0.0.1
npm ERR! Found: @angular/comp...@10.0.14
npm ERR! node_modules/@angular/compiler
npm ERR! dev @angular/compiler@"~10.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"10.2.1" from @angular/loca...@10.2.1
npm ERR! node_modules/@angular/localize
npm ERR! peer @angular/localize@"^10.0.0" from @ng-bootstrap/ng-boo...@7.0.0
npm ERR! node_modules/@ng-bootstrap/ng-bootstrap
npm ERR! @ng-bootstrap/ng-bootstrap@"7.0.0" from the root project

To try and fix this, I upgraded all dependencies using “ncu -u” and then had to downgrade zone.js.

Seems like a rabbit home I’m going down. Any ideas what’s causing these issues?

➜ ~ npm --version
7.0.3
➜ ~ node --version
v15.0.1

After running the above commands, I decided to downgrade to Node 14. Apparently, when I upgraded Yarn earlier today, it upgraded Node.js too.

➜ ~ node --version
v14.15.0
➜ ~ npm --version
6.14.8

This works!

Is Node 15 more strict about dependencies? Any ideas how to fix things for Node.js 15 users?

Thanks,

Matt

[Anthony Viard]

Hi Matt,

I have no ideas about this issue but basically we suggest to use LTS version for node due to issues with non LTS one.

I think it's in our official doc, we do not support non LTS version (or it's just a suggestion, not sure).

Good luck

Ps: if you find a with rabbit, please avoid to follow him ;) 

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/883DA8E1-A825-4457-BB80-779FAF6A7878%40raibledesigns.com.

[Pascal GRIMAUD]

Hi,

Anthony is right. We recommend to use Node LTS because the last version of Node has always been instable. 

In the past, we had daily builds with last version of Node, but it was regularly broken, so the daily builds for last version of Node were dropped when I migrated from Travis to Azure, or from Azure to GitHub Actions (don't remember).

Pascal

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/CAPEJTRen88PtPE3iiqvuA_D27cXekVtLuj2kGPvuveb%2BbOdeWw%40mail.gmail.com.

[Marcelo Boveto Shima]

> Is Node 15 more strict about dependencies? Any ideas how to fix things for Node.js 15 users?

Hello.

NPM 7 is.

It installs peer dependencies and check peer dependencies conflicts.
There will be a transition where a lot of packages will have peer dependencies conflicts.

Example @angular/core has a peer dependencies on zone.js ^0.10.3, so it conflicts with zone.js 0.11.2.
I downgraded zone.js to 0.10.3 otherwise angular would be not installable in npm 7.

Currently Vue and React generated projects are not installable on npm 7.

Regards.

[Kaido Hallik]

As ng-jhipster seems to be pain both for us and for people who generate
Angular front end then I propose to move all still used functionality to
generator-jhipster and archive ng-jhipster after that.

Kaido.

>To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/38A30B09-4BF8-4810-A5A8-AE19557DDB64%40gmail.com.

[Daniel Franco]

++1

This is less dependency and can be changed directly in the application.

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/emcd2048ee-ff20-493a-8092-3cb540167225%40sille.

[Pascal GRIMAUD]

So there is this ticket: https://github.com/jhipster/generator-jhipster/issues/12909

If I understand well, we'll move all code in ng-jhipster to main generator-jhipster

Hope everyone is OK ! If not, comment plz !

I don't use Angular, so I don't have strong opinion on this.

Pascal

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/CADVdDoY43cUKfV6McNJ8MNmFbGeyA%3DjwDO7-tneci4_RhhY6MA%40mail.gmail.com.