Use content-tag so that we can work on Safari / iOS

[NullVoxPopuli]

Pending:

• Ensure and test that running in the browser is appropriately supported embroider-build/content-tag#11
• Enable browser / cross-platform support embroider-build/content-tag#18

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 73ae37c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[patricklx]

I've made a babel version of content-tag if that helps you.
https://github.com/patricklx/ember-template-tag

[NullVoxPopuli]

3.9KB is certainly more attractive than > 741Kb

Though, I already have all of babel in the repl (which is approaching 5 MB). I wonder if there there is any benefit to moving all of my infra to SWC for parsing / compiling via WASM instead of babel.

Right now, 3.9KB is fantastic. (Keeps me under 5 MB in transpilation assets).

I need to look in to switching to SWC though -- maybe it's doable -- would need to figure out if they support legacy decorators -- or wait until @ef4's work with supporting both legacy decorators and spec-decorators... and then just have less transpilation in general.

[NullVoxPopuli]

@patricklx it was not so easy 🙃 I opened a couple issues on your repo, and opened this PR for ember-template-tag: #1168

[github-actions]

Project	Preview URL
Limber	https://368d5c7c.limber-glimdown.pages.dev
Tutorial	https://cb3838be.limber-glimmer-tutorial.pages.dev

Logs