Use new copy_files build mode with Flow templates

[isaacroldan]

WHY are these changes introduced?

Simplifies the flow template extension build process by using the existing copy_files mode instead of a custom flow mode.

WHAT is this pull request doing?

• Removes the custom flow build mode and replaces it with the more generic copy_files mode for flow template extensions
• Updates the outputFileName logic to handle all build modes correctly
• Simplifies the build process by removing the separate bundling step for theme extensions
• Removes unused flow template utility files and functions

How to test your changes?

1. Create a new app with a flow template extension
2. Run npm run dev to verify the extension builds correctly
3. Verify that the flow template files (*.flow, *.json, *.toml) are properly copied to the output directory

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[isaacroldan]

• Use new copy_files build mode with Flow templates #6309 : 2 dependent PRs (#6311 , #6341 ) 👈 (View in Graphite)
• Add new copy_files build mode #6308
• Move buildMode to specification #6305 : 1 other dependent PR (#6306 )
• Remove bundling feature #6303
• main

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

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	78.69% (+0.06% 🔼)	13525/17187
🟡	Branches	72.71% (+0.05% 🔼)	6566/9031
🟡	Functions	78.97% (+0.04% 🔼)	3511/4446
🟡	Lines	79.05% (+0.07% 🔼)	12784/16172

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / flow_template.ts	30.77% (-7.69% 🔻)	0%	0% (-20% 🔻)	30.77% (-7.69% 🔻)

Test suite run success

3243 tests passing in 1359 suites.

Report generated by 🧪jest coverage report action from beddeeb

[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]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/common/version.d.ts

@@ -1 +1 @@
-export declare const CLI_KIT_VERSION = "3.84.1";
\ No newline at end of file
+export declare const CLI_KIT_VERSION = "3.84.0";
\ No newline at end of file

packages/cli-kit/dist/private/node/analytics/error-categorizer.d.ts

@@ -1,5 +1,4 @@
 export declare enum ErrorCategory {
-    Liquid = "LIQUID",
     ThemeCheck = "THEME_CHECK",
     Network = "NETWORK",
     FileSystem = "FILE_SYSTEM",
@@ -7,12 +6,7 @@ export declare enum ErrorCategory {
     Validation = "VALIDATION",
     Permission = "PERMISSION",
     RateLimit = "RATE_LIMIT",
-    Json = "JSON",
+    Parsing = "PARSING",
     Unknown = "UNKNOWN"
 }
-export declare function categorizeError(error: unknown): ErrorCategory;
-/**
- * Formats an error message for analytics tracking, preserving important information
- * based on the error category while keeping it concise and normalized.
- */
-export declare function formatErrorMessage(error: unknown, category: ErrorCategory): string;
\ No newline at end of file
+export declare function categorizeError(error: unknown): ErrorCategory;
\ No newline at end of file

[gonzaloriestra]

/snapit

[github-actions]

🫰✨ Thanks @gonzaloriestra! Your snapshot has been published to npm.

Test the snapshot by installing your package globally:

npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20250916102642

Caution

After installing, validate the version by running just shopify in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.

[gonzaloriestra]

Tested that works as expected 👌