I create yarn version.

[tanmen]

I usually use it with yarn. When installing with jetbrains-npm, package-lock.json was created and I wanted to create a yarn version. So I created jetbrains-yarn. Is it okay?

[jasonkarns]

Would you be interested in opening a pull request? I would be interested in having the yarn shim included in this project as well. The only difference is that we'd want the yarn shim to be opt-in. Since npm is included automatically with node, it's assumed that npm exists in PATH. However, inserting a yarn shim into PATH automatically could potentially be adding a bin for users that don't already have yarn installed. So we'll have to figure out a way to allow users to opt-in to the yarn shim. But I like the idea of having it all in one plugin.

Sidenote: I strongly recommend adding .idea to your user gitignore so that those files aren't accidentally committed to a repo. These should be excluded: https://github.com/tanmen/jetbrains-yarn/tree/master/.idea

[tanmen]

Thank you for your reply! I already know the problem with opt-in. I didn't know how to solve that problem, so I split the repository. Once I know how to opt-in, I create a PR :)

Sidenote: I was only thinking about sharing the same settings with anyone using the jetbrains product. I didn't understand why I strongly denied it.