Repository navigation
Closed as duplicate
Labels
Description
Describe the bug
when I use vp dev,it run,no error
when I use vp check,it run error
maybe I use import createVitePlugins from './vite/plugins';
I use import createVitePlugins from './vite/plugins/index,ts' it can run;
it a error or not?
I need your help
Reproduction
none
Steps to reproduce
No response
System Info
vp v0.1.18
Local vite-plus:
vite-plus v0.1.18
Tools:
vite v8.0.8
rolldown v1.0.0-rc.15
vitest v4.1.4
oxfmt v0.45.0
oxlint v1.60.0
oxlint-tsgolint v0.20.0
tsdown v0.21.8
Environment:
Package manager npm v11.12.1
Node.js v24.14.0 (.node-version)
Environment:
Version 24.14.0
Source .node-version
Source Path D:\code\vite_admin_web_vitePlus\.node-version
Project Root D:\code\vite_admin_web_vitePlus
Tool Paths:
node E:\NVM\vitePlus\js_runtime\node\24.14.0\node.exe
npm E:\NVM\vitePlus\js_runtime\node\24.14.0\npm.cmd
npx E:\NVM\vitePlus\js_runtime\node\24.14.0\npx.cmdUsed Package Manager
npm
Logs
error: Formatting could not start
Failed to load configuration file.
D:/code/vite_admin_web_vitePlus/vite.config.ts
Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'D:\code\vite_admin_web_vitePlus\vite\plugins\index' imported from D:\code\vite_admin_web_vitePlus\vite.config.ts
Ensure the file has a valid default export of a JSON-serializable configuration object.
Formatting failed before analysis startedValidations
- Read the Contributing Guidelines.
- Check that there isn't already an issue for the same bug.
- Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
- The provided reproduction is a minimal reproducible example.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
None yet
Effort
None yet
Target date
None yet
Start date
None yet
Activity
chy1247660523 commentedon Apr 20, 2026
leaysgur commentedon Apr 20, 2026
Thanks for the report.
Currently, some
vite.config.tsfiles may not load as-is.#930
github-actions commentedon Apr 20, 2026
Hello @chy1247660523 👋
Please provide a minimal reproduction using a GitHub repository. This helps us understand and resolve your issue much faster.
A good reproduction should be:
If no reproduction is provided, issues labeled
needs reproductionwill be closed after 3 days of inactivity.For more context on why this is required, please read: https://antfu.me/posts/why-reproductions-are-required