Detect every name Vite resolves its config from

[tricknotes]

PathSet#vite? decides whether an application came from the Vite-based blueprint by looking for a configuration file at its root, and it looked for three names:

%w[vite.config.mjs vite.config.js vite.config.ts]

Vite resolves its configuration from six. Taken from the resolver in vite@8.2.2:

vite.config.cjs  vite.config.cts  vite.config.js
vite.config.mjs  vite.config.mts  vite.config.ts

So an application configured in vite.config.mts, vite.config.cts or vite.config.cjs was taken for a classic one.

What that costs

In development a classic application is served by ember build --watch, which a Vite-based project refuses. Renaming the config of an ember-cli 7.2.0 application to vite.config.mts and asking the gem about it, before this change:

config: ["vite.config.mts"]
paths.vite? => false
dev_server? => false

and the first request then fails with:

:frontend has failed to build: The `--watch` option to `ember build` is not
supported in Vite-based projects. Please use `vite dev` instead.

After this change, the same application:

config: ["vite.config.mts"]
paths.vite? => true
dev_server? => true

The change

The six names live in PathSet::VITE_CONFIG_FILES, and vite? checks against it. The specs iterate that constant, so a name added to the list is covered without a new example being written for it.

Tests

• bin/rspec spec/lib/ember_cli/path_set_spec.rb — 55 examples, 0 failures
• bin/rspec spec/lib — 2 failures, both (app_spec.rb:192, app_spec.rb:200) failing identically on main; they need node_modules installed to find the ember binary

🤖 Generated with Claude Code