Framework CLI - Migration v10 to v11

With v11, we switched to using the Fusion Framework itself for CLI operations. This change was made to reduce maintenance and improve consistency by reusing the same framework modules (such as service-discovery, authentication, and HTTP) in both Node.js and browser environments. By leveraging the Fusion Framework directly, CLI features and integrations stay up-to-date and benefit from shared improvements across the ecosystem.

Why This Matters

• Unified experience: The CLI now behaves more like Fusion apps, making it easier to reason about configuration, authentication, and service discovery.
• Reduced duplication: By reusing core modules, bug fixes and new features are shared between CLI and Framework code.
• Performance: The framework is now initialized only when needed (e.g., for HTTP calls or authentication), improving startup time and resource usage.

Package Changes

• The CLI will now resolve source entrypoint by default from src/(index.tsx|ts)|(main.tsx|ts) (unless configured otherwise).
• The CLI will resolve the output entrypoint by main|module in package.json.
  • This is to enable serving the application in preview mode (import.meta.resolve('PACKAGE_NAME')).

Important

Ensure your application is compatible with these changes before upgrading.

{
  "main": "dist/index.js",
}

Vite Configuration File Naming

Breaking Change: The CLI now uses Vite's standard configuration file naming convention.

• Old behavior (v10): CLI looked for app.vite.config.ts
• New behavior (v11): CLI now looks for vite.config.ts (Vite's default)

Warning

Action Required: If you have a app.vite.config.ts file, rename it to vite.config.ts to ensure your Vite configurations are applied correctly in v11.

Important: Using vite.config.ts should be a last resort for custom setups. Instead, prefer configuring your application through the dev-server configuration (dev-server.config.js) to avoid unexpected behavior. The CLI provides higher-level configuration options that are better integrated with the Fusion Framework ecosystem.

Deprecated App Command Aliases

The following fusion-framework-cli app commands have been renamed:

Old Command	New Command
build-pack	pack
build-upload	upload
build-manifest	manifest
build-publish	publish

Warning

Deprecated commands will be removed in the next major release. While they continue to work with warning messages, please migrate to the new commands immediately.

Option Changes

• Removed: --service option
• Use instead: --env for environment selection

Authentication Changes

Authentication behavior has been updated to improve security and consistency:

• For CI/CD and automation: Continue using the FUSION_TOKEN environment variable
• For local development: Use interactive authentication:

  fusion-framework-cli auth login

Migration Checklist

When upgrading from v10 to v11, ensure you:

• Rename Vite configuration file from app.vite.config.ts to vite.config.ts
• Update command names in all scripts and CI/CD pipelines:
  • build-pack → pack
  • build-upload → upload
  • build-manifest → manifest
  • build-publish → publish
• Replace --service with --env for environment selection
• Update local development workflow to use fusion-framework-cli auth login
• Review custom integrations that may depend on CLI startup behavior (now on-demand)
• Update documentation and team guidelines with new command syntax

Getting Help

For additional information:

• Run pnpm fusion-framework-cli app --help to see current command options
• Check the CLI release notes for detailed changes
• Review related documentation: Authentication and Application Commands