Bug: Fix blockset cli failing when path contains spaces

[theodesp]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.

Description

Fixes a bug when blockset cli command fails to complete when a path to the output-folder contains spaces:

Reproduction

The following error happens when you use faust blockset command when running the project root that contains a space in the path:

❯ npm run blockset

> @faustwp/[email protected] blockset
> faust blockset

warn - Could not find FAUST_SECRET_KEY environment variable.
warn - Some functionality may be limited.
info - Faust: Compiling Blocks into /Users/theo.despoudis/Local Sites/my-app/.faust/build
...
ERROR in build
Module not found: Error: Can't resolve './Sites/my-app/.faust/build' in '/Users/theo.despoudis/Local Sites/my-app'
resolve './Sites/my-app/.faust/build' in '/Users/theo.despoudis/Local Sites/my-app'
  using description file: /Users/theo.despoudis/Local Sites/my-app/package.json (relative path: .)
    Field 'browser' doesn't contain a valid alias configuration
    using description file: /Users/theo.despoudis/Local Sites/my-app/package.json (relative path: ./Sites/my-app/.faust/build)
      no extension
        Field 'browser' doesn't contain a valid alias configuration
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build doesn't exist
      .jsx
        Field 'browser' doesn't contain a valid alias configuration
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build.jsx doesn't exist
      .ts
        Field 'browser' doesn't contain a valid alias configuration
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build.ts doesn't exist
      .tsx
        Field 'browser' doesn't contain a valid alias configuration
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build.tsx doesn't exist
      .js
        Field 'browser' doesn't contain a valid alias configuration
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build.js doesn't exist
      .json
        Field 'browser' doesn't contain a valid alias configuration
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build.json doesn't exist
      .wasm
        Field 'browser' doesn't contain a valid alias configuration
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build.wasm doesn't exist
      as directory
        /Users/theo.despoudis/Local Sites/my-app/Sites/my-app/.faust/build doesn't exist

exec command is tokenizing the --output-path causing the issue:

npm verb argv "exec" "wp-scripts" "start" "--package" "@wordpress/scripts" "--loglevel" "verbose" "--" "--no-watch" "--webpack-src-dir=wp-blocks" "--output-path=/Users/theo.despoudis/Local" "Sites/my-app/.faust/build"

Related Issue(s):

Testing

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: 5a4d2b8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@faustwp/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌