Admin app modernization

[NullVoxPopuli]

Issue Summary

Hello! I noticed the admin app is 3.24, which is quite old.

Ember has a lot of very nice features in v6, and the upcoming edition, Polaris.

Since 3.24 -- these are all the features ya'll could have 🎉 :

• gjs/gts - Docs - Interactive Tutorial - REPL
• vite via The V2 App Blueprint, RFC
  • Fast initial build, and instant rebuilds.
• better data patterns
• better reactivity and component patterns and features
• native typescript support (including blueprints)
• typed templates
• helpers can be plain functions
• new APIs (ones that I found most fun, anyway)
  • @cached decorator
  • curryable modifiers via (modifier)
  • curryable helpers / functions via (helper)
  • in-element
  • unique-id
  • the router service has a refresh() method
  • a renderSettled utility for better testing of rendered state before "Settledness" occurs
• any value can be used in any syntax position (components, modifiers, helpers, etc don't need to be in specific places) - https://guides.emberjs.com/release/in-depth-topics/rendering-values/
• improved error messages (and template stacks reported in errors)
• named blocks / slots
• variable locations are now explicitly known, and you never need to wonder where something is defined (this now goes for components, helpers, modifiers, etc, too (when going all in on gjs/gts))
• no more inject as service, you can import { service } from '@ember/service' directly
• as of 6.1, all the addons in the blueprint are v2 addons (v2 addons are "normal npm libraries") which means your app doesn't build them (as your app does with classic / v1 addons)
• no need for RSVP

Is there appetite for updating / receiving PRs that do updates?

Overall - these efforts fit in to the following categories

• be less weird, improve understandability, eliminate magic
• improve compatibility with the broader ecosystem and general / default expectations
• improve performance (of the framework and the tooling)

Of note, I noticed that the monorepo here is using yarn@v1 -- this would need to change as yarn@v1 does a lot of incorrect things with dependencies, and tools like, vite will not allow for it (unless duplicate / incorrect dependencies are desirable haha)

Detailed releases blog entries:

• https://blog.emberjs.com/ember-3-25-released/
• https://blog.emberjs.com/ember-3-26-released/
• https://blog.emberjs.com/ember-3-27-released/
• https://blog.emberjs.com/ember-3-28-released/
• https://blog.emberjs.com/ember-4-0-released/
• https://blog.emberjs.com/ember-4-1-released/
• https://blog.emberjs.com/ember-4-2-released/
• https://blog.emberjs.com/ember-released-4-3/
• https://blog.emberjs.com/ember-released-4-4/
• https://blog.emberjs.com/ember-4-5-released/
• https://blog.emberjs.com/ember-4-6-released/
• https://blog.emberjs.com/ember-released-4-7/
• https://blog.emberjs.com/ember-4-8-released/
• https://blog.emberjs.com/ember-4-9-released/
• https://blog.emberjs.com/ember-released-4-10/
• https://blog.emberjs.com/ember-released-4-11/
• https://blog.emberjs.com/ember-released-4-12/
• https://blog.emberjs.com/ember-5-0-released/
• https://blog.emberjs.com/ember-released-5-1/
• https://blog.emberjs.com/ember-released-5-2/
• https://blog.emberjs.com/ember-released-5-3/
• https://blog.emberjs.com/ember-released-5-4/
• https://blog.emberjs.com/ember-released-5-5/
• https://blog.emberjs.com/ember-released-5-6/
• https://blog.emberjs.com/ember-released-5-7/
• https://blog.emberjs.com/ember-released-5-8/
• https://blog.emberjs.com/ember-released-5-9/
• https://blog.emberjs.com/ember-released-5-10/
• https://blog.emberjs.com/ember-released-5-11/
• https://blog.emberjs.com/ember-released-5-12/

Steps to Reproduce

I was poking around here: https://github.com/TryGhost/Ghost/blob/main/ghost/admin/package.json#L120

In particular ember-source 3.24 -> 3.28 should be super easy, as it's all non-breaking changes and you get a lot of really good features at 3.28, including gjs/gts.

Code of Conduct

• [X] I agree to be friendly and polite to people in this repository

[NullVoxPopuli]

Why, @Linear? it's rude to close without explanation 😢

[9larsons]

Sorry! I definitely did not mean to close the Github issue.