@equinor/fusion-framework-cli 11.0.0 → 11.0.1

package/dist/esm/version.js

@@ -1,3 +1,3 @@
 // Generated by genversion.
-export const version = '11.0.0';
+export const version = '11.0.1';
 //# sourceMappingURL=version.js.map

package/dist/types/version.d.ts

@@ -1 +1 @@
-export declare const version = "11.0.0";
+export declare const version = "11.0.1";

package/docs/application.md

@@ -1,71 +1,10 @@
----
-title: Developing Apps with Fusion Framework CLI
-description: >
-  In-depth guide to building, configuring, and deploying applications using the Fusion Framework CLI. Includes setup, essential commands, configuration files, CI/CD best practices, troubleshooting, and advanced tips for modern app development.
-category: cli
-related:
-  - ./auth.md
-  - ./migration-v10-to-v11.md
-tags:
-  - getting-started
-  - app-development
-  - configuration
-  - deployment
-  - ci-cd
-  - commands
-  - troubleshooting
-  - release-management
-  - automation
-  - best-practices
-  - migration
-keywords:
-  - fusion-framework-cli upload
-  - fusion-framework-cli publish
-  - fusion-framework-cli tag
-  - fusion-framework-cli config
-  - fusion-framework-cli build
-  - fusion-framework-cli pack
-  - fusion-framework-cli check
-  - fusion-framework-cli manifest
-  - fusion-framework-cli troubleshooting
-  - fusion-framework-cli deployment
-  - fusion-framework-cli ci-cd
-  - fusion app upload
-  - fusion app publish
-  - fusion app tag
-  - fusion app config
-  - fusion app build
-  - fusion app pack
-  - fusion app check
-  - fusion app manifest
-  - fusion app troubleshooting
-  - fusion app deployment
-  - fusion app ci-cd
-  - fusion cli command reference
-  - fusion cli options
-  - fusion cli arguments
----
-
-# Fusion Framework CLI: Application Development Guide
-
-> **Table of Contents**
-> - [Getting Started](#getting-started)
-> - [Prerequisites](#prerequisites)
-> - [Troubleshooting & FAQ](#troubleshooting--faq)
-> - [Configuration](#configuration)
-> - [CI/CD Best Practices](#cicd)
-> - [Command Reference](#commands)
-> - [Migration & Deprecated Commands](#aliases)
-
----
-
 The Fusion Framework CLI empowers you to rapidly build, configure, and deploy modern applications with ease. Whether you’re starting a new project or maintaining an existing app, this CLI streamlines your workflow—from local development to production deployment.
 
 This guide will help you get set up, understand the most important commands, and follow best practices for configuration and CI/CD. Let’s get started building robust, scalable apps with Fusion Framework!
 
 ## Getting Started
 
-### 1. Install the CLI
+### Install the CLI
 
 ```sh
 pnpm add -D @equinor/fusion-framework-cli
@@ -73,7 +12,7 @@ pnpm add -D @equinor/fusion-framework-cli
 npm install --save-dev @equinor/fusion-framework-cli
 ```
 
-### 2. Scaffold a New App (if supported)
+### Scaffold a New App (if supported)
 
 > **Tip:** If you have a template or starter, clone it. Otherwise, create a new directory and initialize your project as below.
 
@@ -82,7 +21,7 @@ mkdir my-fusion-app && cd my-fusion-app
 pnpm init
 ```
 
-### 3. Create Required Files
+### Create Required Files
 
 #### Minimal `package.json` Example
 
@@ -140,13 +79,13 @@ export default defineAppConfig((env, args) => ({
 }));
 ```
 
-### 4. Start the Development Server
+### Start the Development Server
 
 ```sh
 pnpm fusion-framework-cli dev
 ```
 
-### 5. Log in to Fusion Framework (if needed)
+### Log in to Fusion Framework (if needed)
 
 > [!NOTE] 
 > __All HTTP requests to Fusion services require an authorized user.__  
@@ -155,7 +94,7 @@ pnpm fusion-framework-cli dev
 > [!WARNING]
 > The `fusion-framework-cli auth login` command is only available in interactive environments (such as your local terminal). For CI/CD pipelines or automated deployments, you must provide a valid authentication token using the `FUSION_TOKEN` environment variable.  
 >  
-> See [Authentication](./auth.md#setting-the-fusion-token-in-github) for details on setting up tokens for CI/CD.
+> See [Authentication](auth.md#setting-the-fusion-token-in-github) for details on setting up tokens for CI/CD.
 
 ```sh
 pnpm fusion-framework-cli auth login
@@ -317,7 +256,7 @@ jobs:
 ```
 
 > [!TIP]
-> see [setting-the-fusion-token-in-github](./auth.md#setting-the-fusion-token-in-github) for adding `FUSION_TOKEN` to your envirnoment
+> see [setting-the-fusion-token-in-github](auth.md#setting-the-fusion-token-in-github) for adding `FUSION_TOKEN` to your environment
 
 
 ### Example: Using Environment Variables in App Config
@@ -689,11 +628,11 @@ pnpm fusion-framework-cli build-pack
 
 > [!WARNING]
 > The deprecated commands will be removed in future versions. Please update your scripts and workflows to use the new command names (`pack`, `upload`, `manifest`, `publish`) to ensure compatibility with v11 and beyond.
-> For a full migration guide, see [Migration v10 to v11](./migration-v10-to-v11.md).
+> For a full migration guide, see [Migration v10 to v11](migration-v10-to-v11.md).
 
 ---
 
 > **Need more examples?**
-> - See the [cookbooks/](../../cookbooks/) directory for real-world app examples.
-> - For migration help, see [Migration v10 to v11](./migration-v10-to-v11.md).
-> - For advanced configuration, see [Authentication](./auth.md) and [CI/CD](#cicd).
+> - See the [cookbooks directory in the GitHub repository](https://github.com/equinor/fusion-framework/tree/main/cookbooks) for real-world app examples.
+> - For migration help, see [Migration v10 to v11](migration-v10-to-v11.md).
+> - For advanced configuration, see [Authentication](auth.md) and [CI/CD](#ci-cd).

package/docs/auth.md

@@ -1,49 +1,6 @@
----
-title: Fusion Framework CLI - Authorization
-description: >
-  Comprehensive guide to authentication and authorization in the Fusion Framework CLI, covering Azure AD, MSAL, local development, CI/CD, service principals, and best practices for secure automation and integration.
-category: cli
-related:
-  - '@equinor/fusion-framework-module-msal-node/README.md'
-tags:
-  - cli
-  - fusion-framework
-  - msal
-  - azure
-  - azure-ad
-  - authentication
-  - authorization
-  - service-principal
-  - github-actions
-  - ci
-  - cd
-  - devops
-  - security
-keywords:
-  - azure ad
-  - msal
-  - access token
-  - authentication flow
-  - interactive login
-  - silent authentication
-  - token caching
-  - secure storage
-  - app registration
-  - tenant id
-  - client id
-  - scopes
-  - api permissions
-  - oidc
-  - sso
-  - cloud identity
-  - developer experience
----
-
-# Authentication with Fusion Framework CLI
-
 The Fusion Framework CLI provides secure, robust authentication for both automation and interactive development scenarios by leveraging Microsoft's MSAL (Microsoft Authentication Library) and Azure Active Directory (Azure AD). Authentication is handled through the Fusion Framework for Node.js, using the `@equinor/fusion-framework-module-msal-node` package, which is built on top of Microsoft's official `msal-node` library. This ensures standards-compliant, up-to-date authentication flows and seamless integration across Fusion Framework applications and tools.
 
-Key features include:
+## Key features
 - **Multiple authentication modes:**
   - `token_only`: Use a pre-provided token (e.g., for CI/CD and automation).
   - `silent`: Acquire tokens silently using cached or refresh tokens (background services, scripts).

package/docs/libsecret.md

@@ -1,34 +1,3 @@
----
-title: Enabling Secure Credential Storage with libsecret
-description: Instructions for installing libsecret on Linux to enable secure credential storage for your CLI.
-tags: 
-  - cli
-  - authentication
-  - keytar
-  - libsecret
-  - linux
-  - security
-  - credentials
-  - msal
-  - nodejs
-  - keychain
-keywords:
-  - secure credential storage
-  - keychain
-  - linux
-  - node.js
-  - password manager
-  - system keyring
-  - msal-node
-  - credential storage
-  - cross-platform
-  - token caching
-  - npm
-  - secrets
-  - cli authentication
-  - keytar troubleshooting
----
-
 This CLI enables secure authentication and persistent token caching by storing credentials in your system's keychain. It uses [`@azure/msal-node`](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node) for authentication, which relies on the [`keytar`](https://github.com/atom/node-keytar) module for secure credential storage.
 
 > **What is `libsecret`?**  

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,7 +5,19 @@ 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.
 
-## Command Changes
+## 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",
+> }
+> ```
 
 ### Deprecated App Command Aliases
 
@@ -67,15 +51,15 @@ Authentication behavior has been updated to improve security and consistency:
 
 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
+- **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
 

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,6 +1,6 @@
 {
   "name": "@equinor/fusion-framework-cli",
-  "version": "11.0.0",
+  "version": "11.0.1",
   "keywords": [
     "Fusion",
     "Fusion Framework",
@@ -100,10 +100,10 @@
     "read-package-up": "^11.0.0",
     "vite": "^6.3.5",
     "zod": "^3.25.76",
-    "@equinor/fusion-framework-dev-portal": "^1.0.0",
+    "@equinor/fusion-framework-dev-portal": "^1.0.1",
     "@equinor/fusion-framework-dev-server": "^1.0.0",
-    "@equinor/fusion-framework-module-msal-node": "^1.0.0",
-    "@equinor/fusion-imports": "^1.1.1"
+    "@equinor/fusion-imports": "^1.1.1",
+    "@equinor/fusion-framework-module-msal-node": "^1.0.1"
   },
   "devDependencies": {
     "@rollup/plugin-commonjs": "^28.0.3",
@@ -113,7 +113,7 @@
     "@types/adm-zip": "^0.5.0",
     "adm-zip": "^0.5.10",
     "ajv": "^8.17.1",
-    "chalk": "^5.3.0",
+    "chalk": "^5.6.0",
     "is-ci": "^4.1.0",
     "open": "^10.1.1",
     "pretty-bytes": "^7.0.0",
@@ -122,8 +122,8 @@
     "rxjs": "^7.8.1",
     "type-fest": "^4.40.0",
     "typescript": "^5.8.2",
-    "@equinor/fusion-framework-module-app": "^6.1.17",
     "@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"
   },