We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
3.3.8
https://github.com/b12k/vue-sfc-compiler-issue
Can be reproduced by simply extending unit test with additional condition. https://github.com/vuejs/core/pull/9478/files#diff-ba884e3c055eca4af5d6c4a16daa31397a191ceabac0a4018a2b612b781360b5R484-R489
yarn install
dev
build
src/client/components/home/home-message.vue
It should be possible to import type definitions from outer folders.
[@vue/compiler-sfc] Failed to resolve import source "../outer-folder"
System: OS: Windows 11 Pro Binaries: Node: 20.9.0 - ~\AppData\Local\fnm_multishells\70852_1699634305330\node.EXE Yarn: 1.22.19 - ~\AppData\Local\fnm_multishells\70852_1699634305330\yarn.CMD npmPackages: vue: 3.3.8 => 3.3.8
This PR #9478 fixes this issue.
The text was updated successfully, but these errors were encountered:
fix(compiler-sfc): malformed filename on windows using path.posix.joi…
f18a174
…n() (#9478) Closes: #8671, #9583 Not fixed with: #9446 Related: #9473
No branches or pull requests
Vue version
3.3.8
Link to minimal reproduction
https://github.com/b12k/vue-sfc-compiler-issue
Steps to reproduce
Easy way:
Can be reproduced by simply extending unit test with additional condition.
https://github.com/vuejs/core/pull/9478/files#diff-ba884e3c055eca4af5d6c4a16daa31397a191ceabac0a4018a2b612b781360b5R484-R489
See with own eyes way:
yarn install
dev
orbuild
src/client/components/home/home-message.vue
dev
orbuild
What is expected?
It should be possible to import type definitions from outer folders.
What is actually happening?
[@vue/compiler-sfc] Failed to resolve import source "../outer-folder"
System Info
Any additional comments?
This PR #9478 fixes this issue.
The text was updated successfully, but these errors were encountered: