Gutenberg: v0.8.1 of @wordpress/create-block "Minimum system requirements not met!"

[mattwatsoncodes]

Describe the bug
With version 0.8.1 of the @wordpress/create-block script, I always get the error "Minimum system requirements not met!"

Node version: v13.8.0
npm version: 6.14.0

Running npm init @wordpress/[email protected] works fine, so is definitely an issue with the latest version.

To reproduce
Steps to reproduce the behavior:

1. run npm init @wordpress/block
2. "Minimum system requirements not met!" error given

Expected behavior
The script should run in interactive mode.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS 10.15.3
• Terminal: zsh (also tested with bash with same issue)

[mattwatsoncodes]

Note that if I have an existing package.json file and runnpm install check-node-version --save-dev then if I run npm init @wordpress/block the script does run. So looks like it could be a missing dependancy.

It is also worth noting that the script runs fine if I install the block with npm install @wordpress/create-block first, however this does create a package.json and node_modules folder inside my website, whereas with v0.8.0 this was not the case.

Likely a non issue if that is now the expected behaviour.

[gziolo]

I was able to replicate this issue. It's very strange. I plan to investigate it further.

[gziolo]

Let's try to explicitly pass node and npm versions as proposed in https://github.com/WordPress/gutenberg/pull/20456. I'll publish shortly to npm to see if it helps.

I tried both npx @wordpress/create-block and npm init @wordpress/block – they fail when commands are executed in a folder without package.json. I tested it inside Gutenberg repository after release where it works 🙃

[gziolo]

20456 didn't help. We probably need to use Node API instead.

[gziolo]

https://github.com/WordPress/gutenberg/pull/20461 - another attempt :)

[gziolo]

It works correctly with the latest version: 0.8.3. Can you confirm on your end?

[mattwatsoncodes]

@gziolo I can confirm that it is now working at this end! Thank you :)