fix: move config related methods to 'vitest/node'

[pd4d10]

closes #764

[netlify]

✔️ Deploy Preview for vitest-dev ready!

🔨 Explore the source changes: fd9b8fd

🔍 Inspect the deploy log: https://app.netlify.com/sites/vitest-dev/deploys/620caac5b161e70007b3a740

😎 Browse the preview: https://deploy-preview-765--vitest-dev.netlify.app

[sheremet-va]

I think we have some tests with vitest.config.ts. Can you import defineConfig from vitest/node there instead of vite to be consistent? And to check if it's working properly

[pd4d10]

I think we have some tests with vitest.config.ts. Can you import defineConfig from vitest/node there instead of vite to be consistent? And to check if it's working properly

OK. I'll check it later.

[pd4d10]

vitest.config.mjs works (which is the way I use it), while .js and .ts don't. Error message:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './node' is not defined by "exports" in /xxx/node_modules/vitest/package.json

The reason seems to be that js/ts config are treated as cjs in vite, while vitest doesn't have an entry point for exporting cjs.

Shall we add a cjs entry? We may need to do some tweaks in the rollup config.

[sheremet-va]

vitest.config.mjs works (which is the way I use it), while .js and .ts don't. Error message:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './node' is not defined by "exports" in /xxx/node_modules/vitest/package.json

The reason seems to be that js/ts config are treated as cjs in vite, while vitest doesn't have an entry point for exporting cjs.

Shall we add a cjs entry? We may need to do some tweaks in the rollup config.

Somehow I missed your message. After receiving new issues with this i created a PR: #799