Yarn: Don’t install with create command

I'm currently building an application which will act as an initializer Node project. This means it can be ran with npm init <project>/yarn create <project>.

My issue is that running yarn create ... will install the package globally. I don't want that. As I'm constantly using link to make the local build globally accessible to test, this causes never ending conflicts.

I want yarn create to always get the latest from NPM, execute, and clean up. If I wanted to install the package I'd just install it! I don't understand why my global directory has this binary saved to it. npm init handles this perfectly, but for some reason, yarn create, which is the Yarn alternative, installs the binary globally for both Yarn and NPM.



Read more here: https://stackoverflow.com/questions/66325853/yarn-dont-install-with-create-command

Content Attribution

This content was originally published by Devildude4427 at Recent Questions - Stack Overflow, and is syndicated here via their RSS feed. You can read the original post over there.

%d bloggers like this: