Bug: Force cli package to use @wordpress/scripts

[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

• This PR forces the cli blockset command to use the @wordpress/scripts package as part of the build process avoiding any potential confusion.

Related Issue(s):

Testing

• clean up your node_modules package.
• Install the project dependencies again with npm i.
• run npm run blockset -w examples/next/block-support it should use the --package=@wordpress/scripts in the log files

npm verb argv "exec" "wp-scripts" "start" "--package" "@wordpress/scripts" "--loglevel" "verbose" "--" "--no-watch" "--webpack-src-dir=wp-blocks" "--output-path=/Users/theo.despoudis/Workspace/faustjs/examples/next/block-support/.faust/build"

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: 5c255b7

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

This PR includes changesets to release 2 packages

Name	Type
@faustwp/cli	Patch
@faustwp/block-support-example	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! 🙌

[blakewilson]

Nice @theodesp! Just tested manually and things are now compiling as expected.

[ghost]

I get the following error now if I run yarn blockset:
[webpack-cli] Error: Unknown option '--package=@wordpress/scripts'