Khải

> npm i --fix-lockfile Can you try pnpm i --fix-lockfile?

`pnpm` itself requires Node.js >= 12.17, as seen [here](https://github.com/pnpm/pnpm/releases/tag/v6.0.0): > Node.js v10 support is dropped. At least Node.js v12.17 is required for the package to work So I think this...

**Amendment:** > You intend to drop support for pnpm versions without self-contained binary, correct? If that's the case, why even bother running the self-installer and install it via the npm...

@zkochan When will you resolve my requests for change in this PR?

This action by itself does not require setup-node, and isn't affected by setup-node, so you'll need to add that clarification in the example. I'll be waiting for your PR.

> Are you implying without setup-node this action alone will work? Yes. But only for installing pnpm. User still have to use setup-node to run their own JavaScript code. >...

> So to be on the safer side, so that your actions won't error out, can we always use setup node (though pnpm doesn't need it) as a best practice....

@melMass I will accept a PR that adds a code example that use `pnpm/action-setup` and `actions/setup-node` with `cache` key. There is already a section called "Use cache to reduce installation...

Sadly, I'm stuck [here](https://github.com/ksxnodemodules/typescript-tuple/issues/8) (I actually have been stuck there for longer than the issue). So until it is resolved, no new feature from me.

I don't really want to write type names (such as `should_be_same_bu_without_head`).