-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Description
Environment
- Operating System: Linux
- Node Version: v18.16.1
- Nuxt Version: 3.6.1
- Nitro Version: 2.5.1
- Package Manager: yarn@3.6.0
- Builder: vite
- User Config: -
- Runtime Modules: -
- Build Modules: -
Reproduction
https://github.com/daniluk4000/nuxt-3.4.2-docker-error
- Run
docker-compose up
- Open app.vue with IDE and look at the imports
- Run
sudo yarn dev
(as Docker probably broke file system perms if you are not Mac user) - Look at the fixed imports (using VS Code or non-WSL Webstorm)
Describe the bug
Before Nuxt 3.5.3 update tsconfig paths were generated relatively to current directory
But after Nuxt 3.6.0 update it now has absolute paths
And breaks IDE as Docker has different folder names inside of it:
Additional context
This also breaks Webstorm when using with WSL, it can't resolve imports as well even without using docker for me.
It would be so good, if this was made for some reason, to optionally opt-out and use relative paths.
Logs
No response
tomsdob, Jannick94, RvtRebel, mbreit, szhorvath and 16 more