@equinor/fusion-framework-cli 11.0.0-next.8 → 11.0.1

package/docs/migration-v10-to-v11.md

@@ -1,31 +1,3 @@
----
-title: Migration Guide: v10 to v11 CLI Command Changes
-description: >
-  Comprehensive guide to migrating CLI commands from v10 to v11 of the Fusion Framework, including deprecated commands, new command names, authentication changes, and best practices for updating scripts and pipelines.
-category: cli
-related:
-  - ./auth.md
-  - ./application.md
-tags:
-  - cli
-  - fusion-framework
-  - migration
-  - breaking-changes
-  - upgrade
-keywords:
-  - fusion framework
-  - cli commands
-  - v10 to v11 migration
-  - deprecated commands
-  - authentication changes
-  - service discovery
-  - environment configuration
-  - upgrade guide
-  - best practices
----
-
-# Migration Guide: v10 to v11 CLI Command Changes
-
 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
@@ -33,11 +5,23 @@ With v11, we switched to using the Fusion Framework itself for CLI operations. T
 - **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.
 
-## Deprecated App Command Aliases
+## 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.
+> ```json
+> {
+>   "main": "dist/index.js",
+> }
+> ```
 
-This guide covers command changes for the `fusion-framework-cli app` scope.
+### Deprecated App Command Aliases
 
-The following table lists the old commands and their new equivalents:
+The following `fusion-framework-cli app` commands have been renamed:
 
 | Old Command    | New Command |
 | -------------- | ----------- |
@@ -46,29 +30,41 @@ The following table lists the old commands and their new equivalents:
 | build-manifest | manifest    |
 | build-publish  | publish     |
 
-When using a deprecated command, the CLI will display a warning message and guide you to use the new command. Deprecated options such as `--service` are no longer supported; use `--env` instead.
-
 > [!WARNING]
-> The deprecated commands will continue to work for now, but they are scheduled for removal in the next major release. Please migrate to the new commands as soon as possible.
+> **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.
 
-### Additional Notes
-- The deprecated `--service` option is no longer supported. Use `--env` for environment selection.
-- Only the new command names will be supported in future versions. Update your CI/CD pipelines and documentation as soon as possible.
-- The deprecated commands are maintained for backward compatibility during the transition to v11, but will be removed in the next major release. Please migrate to the new commands as soon as possible.
+### Option Changes
+- **Removed:** `--service` option
+- **Use instead:** `--env` for environment selection
 
 ## Authentication Changes
-- The `FUSION_TOKEN` environment variable should only be used for CI/CD and automated deployments.
-- For local development, users should authenticate interactively by running:
+
+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:
   ```sh
   fusion-framework-cli auth login
   ```
-  before executing any commands.
 
-## What to Check When Migrating
-- Update all scripts, documentation, and CI/CD pipelines to use the new command names.
-- Remove any usage of the deprecated `--service` option and replace it with `--env`.
-- Ensure your local development workflow uses `fusion-framework-cli auth login` for authentication.
-- Review any custom integrations that may rely on CLI startup behavior, as initialization is now on-demand.
+## Migration Checklist
+
+When upgrading from v10 to v11, ensure you:
+
+- **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 more details, see the CLI release notes or run `pnpm fusion-framework-cli app --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](./auth.md) and [Application Commands](./application.md)
 

package/docs/portal.md

@@ -1,37 +1,3 @@
----
-title: Developing Portals with Fusion Framework CLI
-description: >
-  Guide to building, configuring, and deploying portal templates using the Fusion Framework CLI. Includes setup, essential commands, configuration, troubleshooting, and best practices for portal development.
-category: cli
-related:
-  - ./auth.md
-tags:
-  - portal-development
-  - configuration
-  - deployment
-  - commands
-  - troubleshooting
-  - best-practices
-keywords:
-  - fusion-framework-cli portal
-  - fusion portal dev
-  - fusion portal build
-  - fusion portal pack
-  - fusion portal upload
-  - fusion portal tag
-  - fusion portal manifest
----
-
-# Fusion Framework CLI: Portal Template Development Guide
-
-> **Table of Contents**
-> - [Getting Started](#getting-started)
-> - [Portal Manifest](#portal-manifest)
-> - [Commands](#commands)
-> - [Troubleshooting & FAQ](#troubleshooting--faq)
-
----
-
 The Fusion Framework CLI enables you to build, configure, and deploy **portal templates** for the Fusion ecosystem. These commands are specifically for creating, building, and managing portal templates—not for managing actual portals.
 
 > **What is a Portal Template?**
@@ -44,7 +10,7 @@ This guide covers the essential commands and best practices for developing and m
 
 ## Getting Started
 
-### 1. Install the CLI
+### Install the CLI
 
 ```sh
 pnpm add -D @equinor/fusion-framework-cli
@@ -52,7 +18,7 @@ pnpm add -D @equinor/fusion-framework-cli
 npm install --save-dev @equinor/fusion-framework-cli
 ```
 
-### 2. Scaffold a New Portal
+### Scaffold a New Portal
 
 Create a new directory for your portal and initialize your project:
 
@@ -61,7 +27,7 @@ mkdir my-fusion-portal && cd my-fusion-portal
 pnpm init
 ```
 
-### 3. Create Required Files
+### Create Required Files
 
 - `portal.manifest.ts`: Defines your portal's metadata and configuration.
 - `portal.schema.ts` (optional): Defines the schema for portal configuration.
@@ -275,4 +241,4 @@ pnpm fusion-framework-cli portal schema portal.schema.prod.ts --debug
 
 ---
 
-For advanced configuration and authentication, see [Authentication](./auth.md).
+For advanced configuration and authentication, see [Authentication](auth.md).

package/package.json

@@ -1,7 +1,6 @@
 {
   "name": "@equinor/fusion-framework-cli",
-  "version": "11.0.0-next.8",
-  "homepage": "https://github.com/equinor/fusion-framework",
+  "version": "11.0.1",
   "keywords": [
     "Fusion",
     "Fusion Framework",
@@ -12,12 +11,17 @@
   "publishConfig": {
     "access": "public"
   },
+  "engines": {
+    "node": ">=20.0.0"
+  },
   "files": [
-    "bin",
-    "dist",
-    "docs",
-    "CHANGELOG.md",
-    "README.md"
+    "./bin",
+    "./dist/esm/lib",
+    "./dist/esm/version.js",
+    "./dist/types",
+    "./docs",
+    "./CHANGELOG.md",
+    "./README.md"
   ],
   "type": "module",
   "bin": {
@@ -45,7 +49,43 @@
     },
     "./bin": {
       "types": "./dist/types/bin/index.d.ts",
-      "import": "./bin/build/bin.js"
+      "import": "./bin/build/bin.mjs"
+    },
+    "./lib": {
+      "types": "./dist/types/lib/index.d.ts",
+      "import": "./dist/esm/lib/index.js"
+    },
+    "./utils": {
+      "types": "./dist/types/lib/utils/index.d.ts",
+      "import": "./dist/esm/lib/utils/index.js"
+    },
+    "./package.json": "./package.json",
+    "./README.md": "./README.md",
+    "./CHANGELOG.md": "./CHANGELOG.md"
+  },
+  "typesVersions": {
+    "*": {
+      ".": [
+        "dist/types/lib/index.d.ts"
+      ],
+      "app": [
+        "dist/types/lib/app/index.d.ts"
+      ],
+      "portal": [
+        "dist/types/lib/portal/index.d.ts"
+      ],
+      "dev-server": [
+        "dist/types/lib/dev-server.d.ts"
+      ],
+      "bin": [
+        "dist/types/bin/index.d.ts"
+      ],
+      "lib": [
+        "dist/types/lib/index.d.ts"
+      ],
+      "utils": [
+        "dist/types/lib/utils/index.d.ts"
+      ]
     }
   },
   "repository": {
@@ -54,46 +94,42 @@
     "directory": "packages/cli"
   },
   "dependencies": {
-    "adm-zip": "^0.5.10",
     "commander": "^13.0.0",
-    "keytar": "7.9.0",
+    "deepmerge": "^4.3.1",
     "ora": "^8.0.1",
-    "vite": "^6.3.5",
-    "chalk": "^5.3.0",
     "read-package-up": "^11.0.0",
-    "zod": "^3.25.20",
-    "@equinor/fusion-framework-dev-portal": "^1.0.0-next.2",
-    "@equinor/fusion-framework-dev-server": "^1.0.0-next.4",
-    "@equinor/fusion-imports": "^1.1.1-next.0"
+    "vite": "^6.3.5",
+    "zod": "^3.25.76",
+    "@equinor/fusion-framework-dev-portal": "^1.0.1",
+    "@equinor/fusion-framework-dev-server": "^1.0.0",
+    "@equinor/fusion-imports": "^1.1.1",
+    "@equinor/fusion-framework-module-msal-node": "^1.0.1"
   },
   "devDependencies": {
-    "ajv": "^8.17.1",
-    "pretty-bytes": "^7.0.0",
-    "is-ci": "^4.1.0",
-    "open": "^10.1.1",
-    "lodash.mergewith": "^4.6.2",
-    "type-fest": "^4.40.0",
-    "rollup": "^4.39.0",
     "@rollup/plugin-commonjs": "^28.0.3",
     "@rollup/plugin-json": "^6.1.0",
     "@rollup/plugin-node-resolve": "^16.0.1",
+    "@rollup/plugin-replace": "^6.0.2",
     "@types/adm-zip": "^0.5.0",
-    "@types/lodash.mergewith": "^4.6.9",
-    "@types/node": "^20.11.14",
+    "adm-zip": "^0.5.10",
+    "ajv": "^8.17.1",
+    "chalk": "^5.6.0",
+    "is-ci": "^4.1.0",
+    "open": "^10.1.1",
+    "pretty-bytes": "^7.0.0",
+    "rollup": "^4.46.3",
+    "rollup-plugin-terser": "^7.0.2",
     "rxjs": "^7.8.1",
+    "type-fest": "^4.40.0",
     "typescript": "^5.8.2",
-    "@equinor/fusion-framework-module-app": "^6.1.13",
-    "@equinor/fusion-framework-module-http": "^6.3.3-next.2",
-    "@equinor/fusion-framework-module": "^4.4.3-next.1",
-    "@equinor/fusion-framework-module-msal-node": "^0.1.1-next.2",
-    "@equinor/fusion-framework-module-service-discovery": "^8.0.15-next.2"
+    "@equinor/fusion-framework-module": "^5.0.0",
+    "@equinor/fusion-framework-module-app": "^6.1.17",
+    "@equinor/fusion-framework-module-http": "^6.3.4",
+    "@equinor/fusion-framework-module-service-discovery": "^8.0.18"
   },
   "peerDependenciesMeta": {
     "typescript": {
       "optional": true
-    },
-    "keytar": {
-      "optional": true
     }
   },
   "scripts": {

package/bin/build/bin.js

@@ -1,28 +0,0 @@
-export { b as buildApplication, c as buildPortal, a as bundleApp, d as bundlePortal, g as generateApplicationConfig, e as generatePortalConfig, l as loadPortalManifest, h as pack, p as publishAppConfig, f as publishPortalConfig, s as startAppDevServer } from './portal-config-publish-ezU_DFki.js';
-import 'vite';
-import 'chalk';
-import '@equinor/fusion-imports';
-import '@equinor/fusion-framework-dev-server';
-import 'node:fs';
-import 'node:fs/promises';
-import 'node:path';
-import 'read-package-up';
-import 'node:url';
-import 'node:assert';
-import 'node:child_process';
-import 'zod';
-import 'adm-zip';
-import 'http';
-import 'https';
-import 'crypto';
-import 'buffer';
-import 'stream';
-import 'util';
-import 'fs';
-import 'path';
-import 'node:http';
-import 'node:process';
-import 'node:buffer';
-import 'node:util';
-import 'node:os';
-import 'ora';