Standardize use of scripts in package.json for common tasks

[MehulKChaudhari]

Rendered text

Standardize the use of yarn and npm scripts in the Ember experience

This change encourages developers to use npm or yarn for certain commands when working with Ember applications, rather than using global Ember CLI commands like ember serve. This aligns Ember with norms in the JavaScript community and helps in reducing the confusion around Ember-specific commands.

[NullVoxPopuli]

as an alternative, I would like all options presented all the time, (via global tab system) like how Microsoft and Starbeam do

example:

clicking the tab for pnpm/npm/yarn changes the tabs everywhere

from: https://starbeamjs.com/frameworks/react/1-getting-started.html

[jenweber]

The learning team & friends are building in something like this in order to support TypeScript + JS in our docs. I would love to have all 3 here as well.

[jenweber]

Just adding a note here that I will be the core team champion for this RFC.

[jenweber]

@MehulKChaudhari @Dhanush027 Today the Framework team reviewed this RFC, and they had some suggestions to help make it more broadly applicable! Let me know if you want help making any of these changes:

• Instead of focusing solely on npm start/test, we can revise the "motivation" section and title to be about using the scripts in package.json rather than focusing on npm/yarn. It is the scripts that are the industry standard we want to point to, not necessarily the CLI tool
• We can mention the following commands as examples: test, start, build, and prepare
• We should mention that developers should always refer to Contributing.md for full instructions when working with a new app or addon
• We can include a link to "prior art" of showing npm start in CLI output. Here's when the text was introduced: ember-cli/ember-cli@6c50caa

After we make these revisions, we can communicate that this RFC is in FCP (final comment period) which will be a good opportunity to invite people to take another look, or a look for the first time.

[dhanushkumar-dev]

I'd like to help to make these changes to RFC.

[MehulKChaudhari]

Yes I would like to help with point 2, 3, and 4

[bertdeblock]

👋 Hi, wondering what the status is of this RFC?

[MrChocolatine]

Aesthetic suggestions.

[locks]

@MehulKChaudhari are you able to update the RFC so the checks pass? @jenweber can help you!

[MehulKChaudhari]

@MehulKChaudhari are you able to update the RFC so the checks pass? @jenweber can help you!

sure will do that

[jenweber]

It looks like our linter does not correctly ignore new files in the images folder. Should we merge without a green linter for this one, assuming consensus for the RFC content? Comment out that linter? Someone could fix it real quick in another PR? I would like this to not be blocked by our tooling.

[locks]

@kategengler do you have time to help out with the tooling?

[kategengler]

@locks I am looking at the tooling. It used to ignore the images (really need to figure out automated tests for workflows)

@jenweber I think it is fine to merge over the failures if it has been verified the RFC does pass those checks.

[kategengler]

@jenweber worth nothing you'll have to open the advancement PR yourself using https://github.com/emberjs/rfcs/blob/master/.github/READTHIS.md#trigger-opening-advancement-pryml