From 6f0e71ce8cecf941c409ec6027467f0b3e81414f Mon Sep 17 00:00:00 2001 From: Katie Gengler Date: Thu, 30 Jan 2025 17:18:38 -0500 Subject: [PATCH 1/3] Add RFC to deprecate generating new projects with yarn --- ...9999-deprecate-new-project-yarn-support.md | 73 +++++++++++++++++++ 1 file changed, 73 insertions(+) create mode 100644 text/9999-deprecate-new-project-yarn-support.md diff --git a/text/9999-deprecate-new-project-yarn-support.md b/text/9999-deprecate-new-project-yarn-support.md new file mode 100644 index 0000000000..b43bc85faa --- /dev/null +++ b/text/9999-deprecate-new-project-yarn-support.md @@ -0,0 +1,73 @@ +--- +stage: accepted +start-date: +release-date: +release-versions: +teams: # delete teams that aren't relevant + - cli + - data + - framework + - learning + - steering + - typescript +prs: + accepted: # update this to the PR that you propose your RFC in +project-link: +--- + + + +# Deprecate `--yarn` support for `ember new` + +## Summary + +Deprecate the `--yarn` flat for `ember new`. We believe newly generated projects +will have a better experience using `npm` or `pnpm` as the package manager. + +## Motivation + +`ember-cli` currently only supports `yarn@1.x`. The latest version of `yarn` is `4.x`. +Most contributors to the project are using `npm` or `pnpm` as their package manager and are not motivated +to update `yarn` support. An [open issue to update support](https://github.com/ember-cli/ember-cli/issues/10339) +has been open for over nearly 18 months without being addressed. + +We know that modern `yarn` can be used successfully with Ember projects, but it requires +disabling Yarn's `PnP` feature. Generating a new project also requires some gymnastics to +ensure that the correct version of `yarn` is installed. + +We believe that the best experience for new projects is to use `npm` or `pnpm` as the package manager. + +## Transition Path + +Deprecate the `--yarn` flag to `ember new` and `ember addon`. Remove it from help and documentation. + +For now, we will continue to support existing projects that use `yarn` as their package manager. + + +## How We Teach This + +Remove any documentation of generating projects with `--yarn`. + +## Drawbacks + + +## Alternatives + +We could update support for `yarn` in the ecosystem, but this would likely only happen if an interested +party were to volunteer. + +## Unresolved questions + +> Optional, but suggested for first drafts. What parts of the design are still +TBD? From b8d0d4432ec91efc04719536135b6f1c916ad530 Mon Sep 17 00:00:00 2001 From: Katie Gengler Date: Thu, 30 Jan 2025 17:21:19 -0500 Subject: [PATCH 2/3] Correct filename --- ...yarn-support.md => 1074-deprecate-new-project-yarn-support.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename text/{9999-deprecate-new-project-yarn-support.md => 1074-deprecate-new-project-yarn-support.md} (100%) diff --git a/text/9999-deprecate-new-project-yarn-support.md b/text/1074-deprecate-new-project-yarn-support.md similarity index 100% rename from text/9999-deprecate-new-project-yarn-support.md rename to text/1074-deprecate-new-project-yarn-support.md From bff1f91655aa10d1dd0e48288654bb36af063646 Mon Sep 17 00:00:00 2001 From: Katie Gengler Date: Thu, 30 Jan 2025 17:22:47 -0500 Subject: [PATCH 3/3] Update frontmatter --- text/1074-deprecate-new-project-yarn-support.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/text/1074-deprecate-new-project-yarn-support.md b/text/1074-deprecate-new-project-yarn-support.md index b43bc85faa..f34188fc99 100644 --- a/text/1074-deprecate-new-project-yarn-support.md +++ b/text/1074-deprecate-new-project-yarn-support.md @@ -1,6 +1,6 @@ --- stage: accepted -start-date: +start-date: 2025-01-30T00:00:00.000Z release-date: release-versions: teams: # delete teams that aren't relevant @@ -11,7 +11,7 @@ teams: # delete teams that aren't relevant - steering - typescript prs: - accepted: # update this to the PR that you propose your RFC in + accepted: https://github.com/emberjs/rfcs/pull/1074 project-link: ---