-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Uppy dependencies not requiring @uppy/[email protected]
missing emitSocketProgress
#5557
Comments
A workaround is to manually add |
What versions are you using? If you are on latest versions this shouldn't happen. What is |
My apologies, I meant This is the list I have defined now with Uppy, before explicitly adding
The problem is that |
@TheSeg delete package-lock and node_modules, reinstall dependencies |
@TheSeg can you check if that helps? |
@Murderlon seems like some npm packages have outdated dependencies. For ex. @uppy/xhr-upload 4.2.3 has "@uppy/companion-client": "^4.2.0" instead 4.3.0 and "@uppy/utils": "^6.0.5" instead 6.0.6. |
Reopening if there's further proof this break after clean install. |
Initial checklist
Link to runnable example
No response
Steps to reproduce
In
@uppy/[email protected]
, theemitSocketProgress
file was removed. However, projects that refer to@uppy/companion-client
are set to 4.2.0, which requires@uppy/utils/lib/emitSocketProgress[.ts]
to exist, break the build.Thus building the project with the following is not possible:
@uppy/transloadit
@uppy/uts
@uppy/tus
@uppy/url
Expected behavior
All project dependencies are built to versions matching their support.
@uppy/transloadit
,@uppy/uts
, and@uppy/url
should require@uppy/[email protected]
.Actual behavior
@uppy/transloadit
,@uppy/uts
, and@uppy/url
do not require@uppy/[email protected]
, and thus break due to missingemitSocketProgress
file in@uppy/[email protected]
.The text was updated successfully, but these errors were encountered: