Allow vite config to be defined as a "vite" key in package.json

Clear and concise description of the problem

Similarly to most js mainstream tools (eslint, jest, prettier…), it would be great to be able to define simple vite config directly in the package.json in order to avoid bloating our repos with config files:

{
  "name": "my-simple-package",
  "version": "2.8.0",
  "vite": {
    "define": {
      "process.env": {}
    }
  }
}

Suggested solution

Config resolution could use cosmiconfig which already provides an implementation to look for config both as a file and as a package.json key:

[
  'package.json',
  `.${moduleName}rc`,
  `.${moduleName}rc.json`,
  `.${moduleName}rc.yaml`,
  `.${moduleName}rc.yml`,
  `.${moduleName}rc.js`,
  `.${moduleName}rc.cjs`,
  `${moduleName}.config.js`,
  `${moduleName}.config.cjs`,
]

Alternative

No response

Additional context

Couldn’t find any issue on the topic already.

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn’t already an issue that request the same feature to avoid creating a duplicate.

[dominikg]

I understand what you want, it is just my opinion that adding extra code and dependencies for this to vite isn’t justified.

Theres maybe 1 in 10000 projects that will have a tiny benefit (one less file), while everyone will have to download and execute extra code and vite maintainers have to add/maintain it.

There are tools to hide files from view, you could make it .vite.config.js and use "dev":"vite --config .vite.config.js" in package.json too.

[sodatea]

FYI: https://bundlephobia.com/package/cosmiconfig@7.0.1 https://bundlephobia.com/package/lilconfig@2.0.4