-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
NX Unsupported payload sent to daemon server: {"type":"GLOB","globs":["**/{vite,vitest}.config.{js,ts,mjs,mts,cjs,cts}"]} #26366
Comments
Hey @beeman - Can you confirm that the issue continues if you run |
Hey @AgentEnder, It still gives me the same error as @beeman even after |
I've found a workaround, I had to migrate from |
In 19.2 and higher GLOB is a valid message for the daemon to handle, looking at your attacher daemon server code it's not what should be present in 19.2 though. I think running nx reset, followed by rm -rf node modules and reinstalling may fix it |
Same problem here. Setting up new application. nx reset + deleting node_modules didn't help. Downgrading @nx/react helped. |
This issue has been automatically marked as stale because more information has not been provided within 7 days. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
I try to create a js lib in my repo and get the message above
Expected Behavior
I expect to be able to create a js lib
GitHub Repo
https://github.com/pubkeyapp/verify-solana-wallet/tree/main
Steps to Reproduce
pnpm install
nx g @nx/js:lib --name verify-solana-wallet --unit-test-runner vitest --bundler vite --directory packages/verify-solana-wallet --project-name-and-root-format as-provided --publishable --import-path verify-solana-wallet --verbose
Nx Report
Failure Logs
Package Manager Version
pnpm 9.0.5
Operating System
Additional Information
Using the latest beta to work around another issue - as per this suggestion.
When I run the above command with the DAEMON disabled it works (
NX_DAEMON=false
) as suggested in one of the other issues I faced over the last months.The text was updated successfully, but these errors were encountered: