Remove yarn support

[avdev4j]

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[MathieuAA]

Now that NPM is the only choice, can we remove useNpm too? As it's always true now
I'm thinking about:

• generator-base.js, https://github.com/jhipster/generator-jhipster/pull/12134/files#diff-fddb513f7a2937b33eb1c1f6a71e64a7R1802,
• same file, https://github.com/jhipster/generator-jhipster/pull/12134/files#diff-fddb513f7a2937b33eb1c1f6a71e64a7R2160
• same file, https://github.com/jhipster/generator-jhipster/pull/12134/files#diff-fddb513f7a2937b33eb1c1f6a71e64a7R2176
• application-options.js, https://github.com/jhipster/generator-jhipster/pull/12134/files#diff-c002265124f07a782478bda07e072063R77

[MathieuAA]

@avdev4j what about this one? ef0d610#diff-fddb513f7a2937b33eb1c1f6a71e64a7R2173 (dest.useNpm = configOptions.useNpm;)
I'm not sure how it's used

[avdev4j]

oups, my bad :D

[yacosta738]

@avdev4j why did you remove the yarn option?

[avdev4j]

hi @yuniel-acosta
Removing Yarn is include in the v7 Roadmap. #10958
I've also open a ticket here :#12135 and explain why we think that is not necessary to maintain Yarn beside Npm:

We notice that Yarn is not use as NPM could be. We added Yarn because it offered more advanced features than NPM in time. Nowadays, NPM has catch up and it's easier for the team to maintain only one package manager.

regards,

[vishal423]

@avdev4j, do we have stats on generation with yarn vs npm ?

[mshima]

I agree with yarn removal, but we should make sure to not conflict with yarn IMO.
Using yarn should be as easy as possible like:

jhipster --client-package-manager yarn
cp my-custom-yarn-package.json package.json
yarn install

I think we should try to:

• move every npm script to package.json
• replace npm calls with packages like npm show with latest-version
• remove npm from every label.
• make sure --skip-install does not call npm.
• keep clientPackageManager for 2 reasons
  ${clientPackageManager} run ... and
  if(clientPackageManager !== undefined && clientPackageManager !== 'npm') { this.warning('Package manager ${clientPackageManager} is not supported.'); skipInstall = true; }

And may we could try to migrate from yarn-lock to package-lock with @npm/arborist.

[mshima]

Use lastest-version package to fetch last version instead of npm show.
Related: #11925 (comment)

[avdev4j]

not sure to understand what you want here

[avdev4j]

Maybe @jdubois can help us to answer that, or anyone else? @jhipster/developers

[mshima]

Removing Yarn is include in the v7 Roadmap. #10958

By the way that v7 Roadmap is more a wish list to me, every contributor added his opinion to it.
I would prefer to keep Logs, Metrics, Configuration, properties and Health admin pages as optional and deprecated for jhipster 7 maybe at a separated generator.

[avdev4j]

By the way that v7 Roadmap is more a wish list to me, every contributor added his opinion to it.

This why I added an issue for that and where we should discuss about it ;).

Basically every v7 item roadmap should has an issue linked with, and to provide a place to discuss. (maybe I forgot few :D)

[deepu105]

Imo its fine to remove yarn and if someone wants to use yarn they can always do so. The script parts with nom will still work

[MathieuAA]

Thanks @avdev4j!!