Piral-cli throws exception about piral HOT 5 CLOSED

I went with the global install because that's what the documentation said, even though there was a disclaimer about it maybe not being the best idea.

I tried it anyway and saw this error pop up so I wanted to give you a heads up. If global installs aren't the way to use the cli and you don't plan on supporting it, especially with pnpm, then no worries—feel free to close the issue.

Cheers

from piral.

Nice, thank you!

from piral.

Is it global installation only? Not sure that works with pnpm and not sure if we can make this work as its quite different to npm / yarn.

Any reason for using the global installation? We usually recommend avoiding the global installation as global installations are generally considered bad practice. The only use case we can think of is for scaffolding, but here solutions such as npm initializers might anyway be better.

from piral.

Well, ideally I'd like to support it, but I think it will be difficult due to the differences... I'll keep this open and either make it a documentation item or solve it - either way it should "work" as documented.

from piral.

Actually it was just a minor thing and it could actually also impact other package managers, even though (in case of npm) that is very unlikely. Thanks for bringing this up - is part of the next release.

from piral.