Tracking issue for making this blueprint the default

[ef4]

• update ember-cli guides
• rename testem.js to testem.cjs
• make sure testem.cjs specifies the tests' output folder. done here
• provide distinct dev vs publish tsconfigs
• re-add multiple ember version matrix testing (@embroider/try or newer lightweight ember-try) Support scenario testing #41
• type=module Set type=module #6
• add a demo index.html (and remove overridden entrypoints config)
• publint and/or are-the-types-wrong
• add skip-git flag
• add skip-npm flag
• ensure there's a clear strategy for self-imports in tests (package.json points at dist, tests build directly against src, so node's default self-importing support will not work). Or explain that you should use subpath imports instead.
  • Add package.json#imports #47
• testem should use --headless=new Set headless=new #45

[NullVoxPopuli]

I think we should also let vite pick the port, rather than choosing 4200

[SergeAstapov]

is this possible already or should be added to the list or should it not be considered possible to do smth like ember test --server?
Was poking into current setup this blueprint provides and I'm not sure it's supported as of now

[NullVoxPopuli]

ember test --server

that's already possible, demo here: https://github.com/NullVoxPopuli/nullui/blob/main/package.json#L64

# Preconfigured scripts to point at config files
":vite": "vite --config ./config/vite.config.mjs",
":testem": "testem --file ./config/testem.cjs",

# Commands easier to read, for better skimming and less visual noise
"build:tests": "pnpm :vite build --mode=test --out-dir dist-tests",
"test:launch": "pnpm :testem server",
"test:ci": "pnpm :testem ci",
"test": "pnpm build:tests && pnpm test:ci",

but it'll be a way better dev experience, if -- instead of re-creating ember test --server, folks use vite dev and visit /tests.
I only discovered this testem stuff because I was debugging something else 🙈