Skip to content

Remove yarn commands in front-end docs #19348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 28, 2023

Conversation

javiereguiluz
Copy link
Member

Related to #19193, we discussed internally about this and we decided to remove all yarn commands. Reasons:

  • Nowadays, npm is as good and fast as yarn
  • Readers without much experience in front-end can just use the npm commands that will work because npm is bundled with Node.js (no need to install other package managers)
  • Readers with lots of experience in front-end can easily adapt the shown npm commands to the package manager that they use: yarn, pnpm, bun, etc.

@OskarStark
Copy link
Contributor

Thank you Javier.

@OskarStark OskarStark merged commit a3ac92c into symfony:5.4 Dec 28, 2023
@OskarStark
Copy link
Contributor

@javiereguiluz can you please make the upmerge? Thanks

@javiereguiluz javiereguiluz deleted the remove_yarn branch December 29, 2023 07:29
@javiereguiluz
Copy link
Member Author

@OskarStark I just upmerged everything 🙏

@OskarStark
Copy link
Contributor

Thank you very much

@ThomasLandauer ThomasLandauer mentioned this pull request Feb 15, 2024
Kocal added a commit to symfony/ux that referenced this pull request Oct 12, 2024
This PR was merged into the 2.x branch.

Discussion
----------

Remove yarn commands in documentations

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT

<!--
Replace this notice by a description of your feature/bugfix.
This will help reviewers and should be a good start for the documentation.

Additionally (see https://symfony.com/releases):
 - Always add tests and ensure they pass.
 - For new features, provide some code snippets to help understand usage.
 - Features and deprecations must be submitted against branch main.
 - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
 - Never break backward compatibility (see https://symfony.com/bc).
-->

Alternative to #1200, for the same reasons explained in symfony/symfony-docs#19348, we don't want to keep `yarn` commands.

Commits
-------

88a3c73 Remove yarn commands in documentations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants