make new package for app execute

[ericlee878]

Resolves: https://github.com/shop/issues-api-foundations/issues/1064

Background

Creating the new shopify app execute CLI command.
This is just the bare bones outline of the CLI command that is basically empty. We will be implementing the command logic into this.

To Test
Use pnpm shopify app execute to test commands during development. This builds and runs the CLI from source without needing to install it globally.

Why regenerate the manifest:

I had to run the pnpm refresh-manifests command to regenerate the manifest. This is because:

• The oclif manifest and README must be updated when adding new commands.
• They contain command metadata for discovery, help documentation, and public docs.

What it added:

• Registered app:execute in oclif.manifest.json with flags and descriptions
• Updated README.md with command documentation
• Without this, the command exists in code but isn't discoverable by the CLI.

[ericlee878]

• make new package for app execute #6587 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	79.25% (-0.03% 🔻)	13608/17171
🟡	Branches	73.15% (+0.01% 🔼)	6652/9094
🟡	Functions	79.34% (-0.02% 🔻)	3507/4420
🟡	Lines	79.61% (-0.03% 🔻)	12853/16145

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / execute.ts	0%	100%	0%	0%

Test suite run success

3358 tests passing in 1372 suites.

Report generated by 🧪jest coverage report action from 53131b7

[jordanverasamy]

looks pretty good, just some Qs

[jordanverasamy]

nice changes ty :)

[jordanverasamy]

still looks good :P

[alexanderMontague]

I'm missing context on what this execute command is intended to do, but scaffolding looks good! Asking about the command intention, because that will change your app return value, ie AppUnlinkedCommand or AppLinkedCommand. Regardless, since it should be run within the context of an app (whether thats authenticated or not), you can probably just return the actual resolved app for now.

Suggested change

	return {app: undefined as unknown as AppInterface}
	const {flags} = await this.parse(Build)
	// ...
	const app = await localAppContext({
	directory: flags.path,
	userProvidedConfigName: flags.config,
	})
	// ...
	return {app}

[ericlee878]

The execute command is basically doing this. But thanks for the feedback, will keep that in mind!

[isaacroldan]

This should be AppLinkedCommand and the app should be obtained using linkedAppContext (as most other commands)

[ericlee878]

Yes, I realized this in my next PR! Will fix this then.

[alexanderMontague]

Scaffolding looks good, and thanks for making it hidden!