-
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
Typescript error caused by wrong import in @uppy/provider-views #5584
Comments
I'm seeing a number of TypeScript errors as well when using the latest version of uppy. Mine seem to originate from Uppy core though I haven't dug too deep. |
Sorry this keeps happening because our editors auto-import something incorrectly 🙄 |
When importing Uppy Core into my TypeScript project via
May this be related to this issue, or a separate topic? |
Can you create a reproducible example in a new issue? Here are some links: |
I have created a reproducible example at https://stackblitz.com/edit/vitejs-vite-twyc9zzx. It is based on Uppy React, just upgraded To see a bunch of TS errors for the |
I think it may be related after all. Putting out a new release now and testing your example afterwards. |
Works as expected now: https://stackblitz.com/edit/vitejs-vite-4vsnw5eg?file=package.json,src%2FApp.tsx |
Awesome, the issues are gone for me locally as well. Thanks a lot for the super quick turnaround. |
Initial checklist
Link to runnable example
No response
Steps to reproduce
This new import in the
@uppy/provider-views
package introduces Typescript compilation errors. It should do an import fromlib
and notsrc
. We are not importing the package explicitly, but it's probably a dependency for the dashboard or the React package.The only solution for now is to have an
override
in ourpackage.json
setting the version to4.3.0
.We already filled an issue a couple weeks ago for a similar issue in the
@uppy/onedrive
package.Expected behavior
Project should build without any errors.
Actual behavior
Project builds with errors.
The text was updated successfully, but these errors were encountered: