Add support for pnpm about create-cycle-app

[zkochan]

As a temporary fix for this, I suggest adding a --skip-install option (the angular-cli has it and I think the ember-cli). Users can just skip installation and manually use pnpm

[SteveALee]

@zkochan Thanks for taking a look.

By default it runs npm to install. And I found when I then run pnpm install it seemed to move things around to be the pnpm config. But I was concerned it was not 'officially' supported. However I found a couple of files were then not found when trying to run the webpack dev server so is not a good solution

Re the error. I rummaged around but got lost. However a better solution is to use the eject script so it does no such resolving lookups.

I'll leave this open for others to comment on adding pnpm support. I'd like to use it. I know @staltz has been using it for his work and also likes it.

[SteveALee]

@zkochan Ah, I was told it does! Thanks for correction.

[zkochan]

So you suggest to run yarn first and then pnpm? pnpm will move folders created by yarn into node_modules/.ignored. pnpm won't reuse anything that was installed by yarn, so this solution would be not optimal.

Regarding the error, I don't know what can be the reason, I need to have a deeper look into it.

[SteveALee]

Closing as the advantage of pnpn is it links to a local cache of packages and latest npm does the same.

[zkochan]

No, npm does not link from the cache. And unlikely will. It copies packages from the cache, like Yarn

[zkochan]

I had discussions about this with the npm team. They are not planning to support linking from the cache