Antoine du Hamel
Antoine du Hamel
@paulm17 to clarify, you don't have to download all the Uppy plugins if you change your code to only import the things you need – if you `import {} from...
@paulm17 to clarify, you don't have to download all the Uppy plugins if you change your code to only import the things you need – if you `import {} from...
> > The workaround is to import the individual modules: > > ```js > > import DragDrop from '@uppy/vue/lib/drag-drop.js' > > import StatusBar from '@uppy/vue/lib/status-bar.js' > > ``` > >...
To clarify, does this error appear on the Companion Node.js console, or on the browser one?
What version of Corepack are you using?
On more recent versions, we've switched the default `COREPACK_HOME` from the user home directory to the AppData one, which might help if you're seeing this because of a permission issue....
> My current workaround is to use `/tmp` (monkey patch, this folder is not the best from security perspective) Can you explain further? What's the security issue with `/tmp`? >...
> I assume yarn installed corepack 0.10.0, because I definitely didn't install it manually myself. It's most likely not Yarn that did that, nvm probably installed Corepack, Corepack 0.10.0 is...
It seems that nvm has a `install-latest-npm` feature (https://github.com/nvm-sh/nvm#migrating-global-packages-while-installing), maybe that also upgrades Corepack (although I doubt it, Corepack is nowhere to be seen in their docmentation). If that doesn't...
> contrived example (created in a pre-caffeinated environment) > > ``` > $ corepack info > > corepack report: > node version: 16.8.0, npm version: 7.21.0 > local package manager...