Advance RFC #0931 "JS Representation of Template Tag" to Stage Recommended

[emberjs-rfcs-bot]

Advance #931 to the Recommended Stage

Rendered

Summary

This pull request is advancing the RFC to the Recommended Stage.

• PR to Accepted Stage: JS Representation of Template Tag #931
• PR to Ready For Release Stage
• PR to Released Stage

An FCP is required before merging this PR to advance.

Recommended Stage Summary

The "Recommended" stage is the final milestone for an RFC. It provides a signal to the wider community to indicate that a feature has been put through its ecosystem paces and is ready to use.

To reach the "Recommended" stage, the following should be true:

If appropriate, the feature is integrated into the tutorial and the guides prose. API documentation is polished and updates are carried through to other areas of API docs that may not directly pertain to the feature.

If the proposal replaces an existing feature, the addon ecosystem has largely updated to work with both old and new features.

If the proposal updates or replaces an existing feature, high-quality codemods are available.

If needed, Ember debugging tools as well as popular IDE support have been updated to support the feature.

If the feature is part of a suite of features that were designed to work together for best ergonomics, the other features are also ready to be "Recommended".

Any criteria for "Recommended" for this proposal that were established in the Ready For Release stage have been met.

An FCP is required to enter this stage. Multiple RFCs may be moved as a batch into "Recommended" with the same PR.

Checklist to move to Recommended

• Criteria specific to this feature: Any additional criteria for "Recommended" for this proposal that were established in the Ready For Release stage have been met.
• Tutorial: If appropriate, the feature is integrated into the tutorial.
• Guides: If appropriate, the feature is integrated into the guides prose.
• API Docs: API documentation is polished and updates are carried through to other areas of API docs that may not directly pertain to the feature.
• Addon Ecosystem: If the proposal replaces an existing feature, the addon ecosystem has largely updated to work with both old and new features.
• Codemods: If the proposal updates or replaces an existing feature, high-quality codemods are available.
• Debugging Tools: If needed, Ember debugging tools (e.g. Ember Inspector, Deprecation Workflow) have been updated to support the feature.
• IDE Support: If needed, popular IDE support has been updated to support the feature.
• Engines, SSR: If needed, ecosystem feature such as Ember Engines, SSR support have been updated to support the feature.
• Blueprints: Blueprints have been updated to support the feature and to reflect the new best practices implied by this feature.
• Linting: Lint rules have been updated or added or removed to support the feature and to reflect the new best practices implied by this feature.
• Deprecations: If this feature implies that other features are no longer best practice, RFCs have been created to deprecate those features.
• Blog Post: Consider if a blog post should be written to introduce this feature to the community.
• Feature Suite: If the feature is part of a suite of features that were designed to work together for best ergonomics, the other features are also ready to be "Recommended".
• FCP to Recommended: 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.

Criteria for moving to Recommended (required)

<-- Copy and paste the criteria for "Recommended" from the Ready For Release stage here -->

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

1. Enable access to the runtime template compiler in classic builds (currently only accessible in embroider). We thought this would be easy but it's not. This will stay an Embroider / v2-App only feature.
2. Add a section to https://guides.emberjs.com/release/components/template-tag-format/ explaining the pure-JS representation and how to use the runtime template compiler.

[ef4]

Status update: the last remaining piece of implementation here was going to be exposing the new runtime template compiler to classic builds. But @kategengler and I discovered that this is not as easy as I first thought, because the new module depends on many existing modules that are already in the AMD shimmed bundles, and it's difficult to use a mix of new-style and old-style modules. Allowing them to duplicate causes serious failures because symbols (like the one for component managers) disagree.

So instead I think this is done, the new runtime template compiler will remain an Embroider (whether webpack or vite) only feature. On the same timeline that we could force classic builds to use Ember's new-style ES modules, we can just deprecate classic builds themselves.

[NullVoxPopuli]

wip: ember-learn/guides-source#2123

[ef4]

the new runtime template compiler will remain an Embroider (whether webpack or vite) only feature.

This is no longer true. On classic builds you can use the new "use-ember-modules" feature to stop using the AMD bundles, in which case the new runtime template compiler should work there too.

[ef4]

Guides PR needs some cleanup to merge.