ENOENT: no such file or directory, rename ... deps_temp #9986
Comments
|
same problem |
|
I've updated the issue description with full vite debug logs when encountering this issue. I also hacked in a little message of my own, that confirms that the rename is happening twice. Here's a small extract from the collapsed logs above. vite:deps ✨ using post-scan optimizer result, the scanner found every used dependency +0ms
vite:deps ✨ using post-scan optimizer result, the scanner found every used dependency +1ms
renaming /Users/ianvs/code/experiments/storybook-coverage-recipes/react_vite/node_modules/.vite-storybook/deps_temp to /Users/ianvs/code/experiments/storybook-coverage-recipes/react_vite/node_modules/.vite-storybook/deps
renaming /Users/ianvs/code/experiments/storybook-coverage-recipes/react_vite/node_modules/.vite-storybook/deps_temp to /Users/ianvs/code/experiments/storybook-coverage-recipes/react_vite/node_modules/.vite-storybook/deps
done renaming
7:15:29 AM [vite] error while updating dependencies:
Error: ENOENT: no such file or directory, rename '/Users/ianvs/code/experiments/storybook-coverage-recipes/react_vite/node_modules/.vite-storybook/deps_temp' -> '/Users/ianvs/code/experiments/storybook-coverage-recipes/react_vite/node_modules/.vite-storybook/deps' |
|
create new folder named |
|
This one might be related. |
|
It works sometimes. |
|
I often encountered this bugs, and generally I'll delete all cache and start vite with |
LGTM |
|
The first time, open the project install dependencies and start the service Local: http://localhost:5555 The node_modules/.vite is empty. I must to end the process, close the previous routing page, start the service again and only open http://localhost:5555 in the browser to access it normally. Env |
|
@IanVS linked this issue, and I'd like to chip in with my own issue too. I have this bug on my I made this repo which explains the issue, and also has instructions on how to reproduce: https://github.com/nikki-cat/vue-vite-storybook-mini-repo I also described a way to consistently "fix" the issue temporarily. I don't know if that gives a clue on what the issue is, but you can read it here: https://github.com/nikki-cat/vue-vite-storybook-mini-repo#somewhat-of-a-workaround oh also, here's some system info: |
|
Thanks for sharing your steps, @XioDone. I think that's the first set of reproduction steps that don't involve Storybook, so it seems that it's not storybook-specific, but perhaps we're reloading vite in a way that's more likely to trigger the underlying bug. |
|
My 2 cents, I am having the same issue. |
|
Deleting Edit: Not always.. still awaiting any fix/workaround. |
This comment was marked as off-topic.
This comment was marked as off-topic.
maybe you can try this, it works on me. set preserveSymlinks to |
Did you work in monorepo(pnpm)? My project crashed directly when I open this option. And here are snapshots. Click to view the snapshotsThis is vite's log from console.
And then the process crashed.
|
|
|
idk if it works for monorepo or no, since mine isn't monorepo. |
|
Here's the code location referring to This issue is causing the SvelteKit CI to fail on Windows quite frequently |
benmccann
added
bug
p3-downstream-blocker
|
Error: ENOENT: no such file or directory, rename '...\node_modules.vite\deps_temp' -> '....\node_modules.vite\deps I have same problem with vite-react |
Thank for your answer!!! it's work for me! |
|
It is crazy but these steps works for me:
Next time when you will want to open a storybook |
this solution worked for me. thank you a lot |
|
Would you try to reproduce this issue with vite@4.2.0-beta.1? I think it should be fixed after: cc @IanVS |
|
The beta seems to fix our problem |
Do any guys know why this process needed? |
|
@songjihyeok please test with vite@4.2.0-beta.2, this issue should be resolved now |
|
That's exciting! Its tough to verify because it's always been intermittent, but I've asked some folks who were having it happen fairly regularly to try upgrading, and will report back. I'll close the issue for now and someone can comment if it still happens for them on 4.2.0-beta.1+. Thanks for the fix! |
|
I'm still getting this issue with 4.2.1 |
|
@MorayM would you create a new issue linked to this one with a minimal reproduction? |
|
@patak-dev I'll try! I encountered it upgrading an existing project from 3.2.5 so it may take a while to peel back all the dependencies. Although I've just downgraded back to 3.2.5 and am getting a slightly different variation on the same error so now I'm not sure what's going on! In 4.2.1 the error message is I have |
|
Just to add - I've seen it still failing in |
|
Ok, let's reopen the issue. |
and others
Describe the bug
Sometimes when Vite is starting up with Storybook, it throws an error as shown below. Normally it's difficult to reproduce, but I've got a set of steps that seems to reliably reproduce the issue (at least, it happened to a storybook maintainer, and I was able to follow the steps as well.
npx storybook@future upgrade --prerelease --yes && yarn storybookbutton.stories.ts,page.stories.ts,header.stories.ts)yarn storybookagainReproduction
https://github.com/yannbf/storybook-coverage-recipes/tree/main/angular_vite
System Info
System: OS: macOS 12.5.1 CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz Memory: 371.49 MB / 32.00 GB Shell: 5.8.1 - /bin/zsh Binaries: Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node Yarn: 1.22.19 - ~/.yarn/bin/yarn npm: 8.12.1 - ~/.nvm/versions/node/v16.14.2/bin/npm Browsers: Brave Browser: 104.1.42.97 Firefox: 104.0.1 Safari: 15.6.1Used Package Manager
yarn
Logs
Click to expand!
Validations
The text was updated successfully, but these errors were encountered: