-
-
Notifications
You must be signed in to change notification settings - Fork 671
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
bug: New partysocket version break deploy cli #1814
Comments
@ericallam Maybe you can put a stable version in the package.json of trigger.dev |
@rharkor could you try adding an override to your package.json to pin // npm
{
"overrides": {
"partysocket": "1.1.0"
}
}
// yarn
{
"resolutions": {
"partysocket": "1.1.0"
}
}
// pnpm should work with the overrides above but could also try
{
"pnpm": {
"overrides": {
"partysocket": "1.1.0"
}
}
} |
Weirdly partysocket hasn't updated their releases for 1.1.1 as of this moment |
I am using npx trigger.dev@latest so this will not work unfortunately. I will find a solution ty |
@rharkor add the |
Actually I needed to add this to my package.json "overrides": {
"trigger.dev": {
"partysocket": "1.1.0"
}
} |
if and when you have the time, can you check whether |
Provide environment information
System:
OS: Linux 6.11 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)
CPU: (24) x64 AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Memory: 20.41 GB / 30.44 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
Describe the bug
Partysocket package released the version 1.1.1, and it seems to break the current trigger deploy method of the cli.
https://www.npmjs.com/package/partysocket?activeTab=versions
Reproduction repo
N/A
To reproduce
Remove the npx cache of trigger:
rm -rf ~/.npm/_npx/f51a09bd0abf5f10
Use the latest version of the cli and try to deploy
Additional information
No response
The text was updated successfully, but these errors were encountered: