For testing this out (without cloning), I published this branch under @nullvoxpopuli/ember-vite-app

So, creating a TS app would happen like:

npx ember-cli@latest new my-app-name \
  --blueprint @nullvoxpopuli/ember-vite-app \
  --pnpm \
  --typescript

The upstream blueprint supports --typescript, and a fair number of folks wanting "to try out the Vite blueprint" want to use TypeScript.

The effort required here isn't huge, mostly config changes.

• get TS working
  • support hbs and the template-registry (should this be opt in/out?) will happen in another PR
• remove/convert TS files for the JS output

The Approach:

• split all files by js/ts based on presence of the --typescript option
  • this makes it easier to maintain each set of files, and compare them
  • previous blueprints trying to inline all the conditions for typescript vs not typescript have proven tricky to maintain, and harder to read than they otherwise could be! (like in this PR!)
  • this also allows easier separation since proper TS support is very invasive to a project -- a lot needs to change

What isn't implemented:

• types registry (for loose mode)
• service registry
• models registry

These will show up in future PRs (as this one is already quite big) -- and how we want to teach ember-data in the future also doesn't include models, so I'll need to sink with @runspired on what the strategy should be there (or if ember-data/warp-drive has its own generator, etc (since it's meant to be very "use what you need"))