Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

As part of #777 to introduce the new Init package, one issue that came up was that when running yarn install as part of the test suite, warnings were getting thrown as errors.

0 passing (3s)
  1 failing

  1) Scaffold Greenwood With Yarn: 
       default minimal template
         "before all" hook in "default minimal template":
     Error: the string "warning @greenwood/cli > markdown-toc > gray-matter > coffee-script@1.12.7: CoffeeScript on NPM has moved to \"coffeescript\" (no hyphen)\n" was thrown, throw an Error :)
      at processTicksAndRejections (node:internal/process/task_queues:93:5)

This would cause the test to fail, though there was nothing really wrong at all.

While using ignore for the stdio does help pass the test

 const process = spawn(pkgCommand, args, { stdio: 'ignore' });

The result would be that users would not get any install logs at all when running @greenwood/init during the install step which is confusing and potentially disruptive, making the user think something has broken and potentially cancelling out the whole operation.

 % npx @greenwood/init --install
-------------------------------------------------------
Initialize Greenwood Template ♻️
-------------------------------------------------------
Initialzing project with files...
Creating manifest (package.json)...
Installing project dependencies...

# terminal just "hangs" here while install happens 

Initializing new project complete!
owenbuckley@Owens-MBP-2 my-app %

Details

Would like to restore this test case while still keeping the stdio setting such that the install logs still show. Not sure if this is something to fix in gallinago or something we can work around in our test setup or not, so making this issue to track and try and resolve.

Here is the PR that reverted the stdio setting and had the relevant specs set to xdescribe. What is interesting is that Windows action passed, but the Linux one failed even for npm. Probably more to do with how process spawning is handled between the too.