"Invalid command: on-resolve" after update from 4.1.4 #14043
Comments
|
We're also seeing this, though it eventually succeeds after throwing out many MB of errors. |
|
Seeing similar errors, but I’m neither using yarn or storybook. Although it does eventually produce a bundle, Netlify recognises it as an error and refuses to publish. Below is a list of my dependencies. Hopefully that’ll help rule out some interfering modules (or whatever the issue may be). |
|
I can't access the repro, is it set to private? I'm not really sure how the error is caused, it seems to be coming from esbuild's default "Javascript plugin" Go plugin that processes all of the JS plugins for esbuild. |
|
Same error here, works with 4.1.4, not working with any of the next version. It works fine with Linux and windows devs but not on macos 😕 |
|
Same error here, with 4.3.2 and 4.4.x not working with both of these versions. Works fine with 4.1.4 only. Here's my system configuration: |
|
Dependency esbuild version ^0.18.10 is automatically upgraded to 0.18.12, and this version of My solution is override vite dep in package.json: "overrides": {
"vite": {
"esbuild": "0.18.10"
}
} |
|
@zhouLion I tried the same but it didn't work. The same error is there. I put the provided code in my package.json, removed node_modules and install the dependencies again. |
|
I tested all (possible) reproductions linked to storybookjs/storybook#22253. But I wasn't able to reproduce any of them.
I noticed that all reports that includes a system info uses Mac. I guess this only happens on Mac. |
Yes, sorry about that - the repo was private. Now public. |
|
I tested using pnpm and received the same issue. I testing the same repo on Linux and did not see the issue. So it could well be a Mac only thing as @sapphi-red said. Config of the linux system for reference: |
|
Temporary Solutions: The pnpm example: pnpm patch fsevents
# edit fsevents.js from output folder
pnpm patch-commit <output-folder> |
|
@yoyo930021 I actually ended up on that same chokidar issue and saw you had linked to it :) I can confirm that the issue I was seeing was the storm of 'unlink' events from |
sapphi-red
added
bug: upstream
|
Closing as a new |
Describe the bug
I have a project that was working successfully with vite 4.1.4, but after updating (I have tried 4.2.2 and now 4.4.9) I fails to run the development server, with hundreds of errors like:
vite buildstill works successfully.This looks similar to the issues mentioned in storybookjs/storybook#22253, but occur when running the development server, not storybook.
The error appears to occur after server reload:
After these errors, the dev server seems to go into a restart loop.
Reproduction
https://github.com/wherethebitsroam/vite-bug
Steps to reproduce
Run
yarn install,yarn vite -d, make a request to localhost:3000Note that this repo is an edited version of
https://github.com/streamlit/streamlit/tree/1.11.0/frontend, which seems to be causing the problem when referenced in our project.System Info
System: OS: macOS 13.5 CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz Memory: 989.44 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.2.0 - /usr/local/bin/node Yarn: 3.3.0 - /usr/local/bin/yarn npm: 9.6.6 - /usr/local/bin/npm Browsers: Chrome: 115.0.5790.170 Firefox: 115.0.3 Safari: 16.6 npmPackages: @vitejs/plugin-react: ^4.0.4 => 4.0.4 vite: ^4.4.9 => 4.4.9Used Package Manager
yarn
Logs
https://github.com/wherethebitsroam/vite-bug/blob/main/vite.log
This log was created by the command:
yarn vite -d |& tee vite.logI had to kill vite to get it to stop restarting.
Validations
The text was updated successfully, but these errors were encountered: