uppy: `@uppy/vue` requires installing dashboard even if it's not used
Initial checklist
- I understand this is a bug report and questions should be posted in the Community Forum
- I searched issues and couldn’t find anything (or linked relevant results below)
Link to runnable example
No response
Steps to reproduce
npm i @uppy/core @uppy/vue @uppy/drag-drop @uppy/status-bar- Only use
DragDropand/orStatusBar:import {DragDrop, StatusBar} from '@uppy/vue' - Build
Expected behavior
Successful build.
@uppy/dashboard,@uppy/drag-drop,@uppy/file-input,@uppy/progress-bar, and@uppy/status-barare now peer dependencies. This means you don’t install all these packages if you only need one. To migrate: install only the packages you need. If you use the Dashboard component, you need @uppy/dashboard, and so onwards.
From https://uppy.io/docs/migration-guides.html#uppy-vue
Actual behavior
Build failure:
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 6
- Comments: 16 (11 by maintainers)
same problem with
@uppy/reactThe workaround is to import the individual modules:
We should probably update the docs to only show imports that targets the individual components modules. We also still have the possibility to put back the uppy plugins as direct dependencies instead of peers in a semver-minor, so if someone feels like it would be a better option, please speak up.
@paulm17 Things changed in v3 as I mentioned above. What I’ll say is, you can upgrade to v3 and the only additional thing you have to do is list
@uppy/dashboardand perhaps one other package in yourpackage.json. Those packages were already getting installed in v2. To confirm, you can run the following command for both v2 and v3:And you’ll notice that it’s there in both cases.
Yep, that is what the maintainers will figure out for this ticket.
@paulm17 It’s still installing them automatically for you, since they’re direct dependencies of
@uppy/react@2.x.xrather than peer-deps in 3.x.x.