Advance #09772 to the Ready For Release Stage

Rendered

Summary

This pull request is advancing the RFC to the Ready For Release Stage.

• PR to Accepted Stage: #09772

An FCP is required before merging this PR to advance.

Upon merging this PR, automation will open a draft PR for this RFC to move to the Released Stage.

Checklist to move to Ready for Release

• Implementation is complete according to plan outlined in the RFC, with any adjustments noted in the RFC
• Any necessary learning materials have been updated
• The Ember team is ready to commit to the stability of any interfaces exposed by the current implementation of the feature. This is the go/no go decision for any feature flags, but the flags should only be turned on when moving to Released.
• The feature may not yet have support by the entire ecosystem (e.g. IDEs, addons, Ember Inspector, Engines, Lint Rules, Blueprints, etc), but it does not unintentionally break any existing functionality in those areas.
• The Interactive Tutorial is not broken by this feature.
• Criteria for moving to the Recommended Stage has been filled out
• This PR has been converted from a draft to a regular PR and the Final Comment Period label has been added to start the FCP
• Each team has been added as a reviewer to the PR at the start of the FCP. Reviews are not required by the end of the FCP. This is a notification step.
  • Framework @emberjs/framework
  • Data @emberjs/ember-data-core
  • CLI @emberjs/cli
  • Learning @emberjs/learning-core
  • Typescript @emberjs/typescript-core
  • Steering @emberjs/steering

Criteria for moving to Recommended (required)

A set of criteria for moving this RFC to the Recommended Stage, following release:

1. Add a page to the Ember Guides to cover "Build Tooling" that points at the Vite docs and explains the basics of how we're using Vite (like the presence of the ember plugin, etc).
2. Add a banner to the old ember-cli guides that points at the new Build Tooling page.
3. For command that shouldn't work in the new format (like ember test -s) we should update them to give a good error message.
4. Somewhere (release notes? A guides page?) we need upgrade notes that explain the status of ember-cli-update and the existence of the codemod.
5. Warn when using --yarn on generation with the new blueprint (it is not supported)
6. --lang option lacks error handling in 6.8.0-beta ember-cli/ember-cli#10828
7. Search guides and API docs for mentions of:
   • ember-auto-import update addons-and-dependencies to be ready for Vite ember-learn/guides-source#2160
   • commands that are no longer recommended like ember test -s
     • ember test update cases of ember test  ember-learn/guides-source#2164
     • ember install chore: remove ember install references ember-learn/guides-source#2163
   • mentions of ember-cli (reviewing which ones are still appropriate)
   • broccoli
   • "assets"
   • "dependencies" / "libraries" / "npm packages"
   • "webpack"
   • "fastboot" / "ssr" (may need to explain your options in terms of the old fastboot implementation and how to use Vite SSR)

Track Implementation

• work ongoing at https://github.com/ember-cli/ember-app-blueprint
• codemod exists https://github.com/mainmatter/ember-vite-codemod
• Ensure generating with classic blueprint works
  • Currently fails with The package '@ember-tooling/classic-build-app-blueprint' is not a valid Ember CLI blueprint.
• Ensure generating with classic blueprint is documented somewhere
  • npx [email protected] new super-rentals -b @ember-tooling/classic-build-app-blueprint
• Inspector support Ember Inspector not detecting application in 6.8.0-beta.3 (Chrome and Firefox) ember-inspector#2686
• ember help should reflect the default blueprint ember-cli/ember-cli#10829