-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Cannot read properties of undefined (reading 'directory') #2141
Comments
+1 |
may I ask how to solve this? |
The previously fixed PR was rolled back due to a bug, so for now, let's define the |
thank you. but i usage scenario is dumi. no existent |
I have tested it but it still failed: dumijs - mfsu |
checkout this:https://github.com/jeffwcx/dumi-vue-demo |
thank you! |
@lifegit I will fix it as soon as possible |
windows system is error: Path contains invalid characters: D:\project.dumi\tmp\plugin-preset-vue:vue3
|
+++++1 demo不靠谱 |
遇到了同样的问题,请问这个 PR 什么时候会发版呢🤔? |
Version
v2.3.8
OS Version
window11 22631.3672
Node.js Version
v20.14.0
Browser Version
Edge 125.0.2535.92
Link to minimal reproduction
None
Steps to reproduce
What is expected?
Can operate normally
What is actually happening?
yarn run v1.22.22
$ npm run dev
info - dumi v2.3.8
info - Vue v3.4.27
fatal - TypeError: Cannot read properties of undefined (reading 'directory')
at Hook.fn (F:\tempDemo\node_modules@dumijs\preset-vue\dist\common.js:42:91)
at F:\tempDemo\node_modules@umijs\core\dist\service\service.js:136:38
at _next6 (eval at create (F:\tempDemo\node_modules@umijs\bundler-utils\compiled\tapable\index.js:1:8410), :85:17)
at eval (eval at create (F:\tempDemo\node_modules@umijs\bundler-utils\compiled\tapable\index.js:1:8410), :110:1)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
fatal - A complete log of this run can be found in:
fatal - F:\tempDemo\node_modules.cache\logger\umi.log
fatal - Consider reporting a GitHub issue on https://github.com/umijs/umi/issues
Done in 3.94s.
Any additional comments? (optional)
None
The text was updated successfully, but these errors were encountered: