@equinor/fusion-framework-cli 10.7.5-apploader-be21a6b60eb13eee8bf869e75002d8634e9c50a9 → 11.0.0-next.1

package/CHANGELOG.md

@@ -1,10 +1,59 @@
 # Change Log
 
-## 10.7.5-apploader-be21a6b60eb13eee8bf869e75002d8634e9c50a9
+## 11.0.0-next.1
 
 ### Patch Changes
 
-- pre-release changeset for tag **apploader**, all public packages are patched
+- [#3075](https://github.com/equinor/fusion-framework/pull/3075) [`f8a4db1`](https://github.com/equinor/fusion-framework/commit/f8a4db1208ef98eea7f6f286087338ee74858434) Thanks [@odinr](https://github.com/odinr)! - Update `.npmignore` and `package.json` to improve package publishing:
+
+  - Ensure `bin` directory is included in published files by updating `.npmignore` and adding it to the `files` array in `package.json`.
+  - Add `repository` field to `package.json` for better metadata.
+
+  These changes help ensure all necessary files are included in the published package and improve discoverability and metadata for consumers.
+
+## 11.0.0-next.0
+
+### Major Changes
+
+- [#3074](https://github.com/equinor/fusion-framework/pull/3074) [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13) Thanks [@odinr](https://github.com/odinr)! - The CLI has been rewritten to use Fusion Framework internally to minimize dependencies and improve performance. This change allows the CLI to be more efficient and maintainable. It also means that the CLI is now a first-class citizen in the Fusion Framework ecosystem, providing a more consistent and integrated experience.
+
+  The dev portal has been moved out to a separate package `@equinor/fusion-framework-dev-server`. This separation allows for a more modular architecture, enabling developers to use the dev portal independently of the CLI. It also facilitates easier updates and maintenance of the dev portal without affecting the CLI functionality. It also allows for 3rd party developers to create their own dev portals using the Fusion Framework. Also, moving the dev portal to a separate package allows for better versioning and dependency management, ensuring that developers can always use the latest features and improvements without being tied to the CLI release cycle.
+
+  The dev portal can be configured using the `dev-server.config.js` file, which allows developers to customize the behavior and appearance of the dev portal. This configuration file provides flexibility in how the dev portal operates, enabling developers to tailor it to their specific needs and preferences. **this is currently not documented, but will be in the future**
+
+  Since the dev portal uses the plugin `@equinor/fusion-framework-vite-plugin-spa`, it is possible to specify a live portal to preview the application in the dev portal. This feature allows developers to see their changes in real-time, enhancing the development experience and speeding up the feedback loop. It is particularly useful for testing and debugging applications during development.
+
+  The dev portal also supports mocking API services, which allows developers to simulate backend services without needing a live server. This feature is particularly useful for testing and development, as it enables developers to work on the frontend independently of the backend, ensuring a smoother development process. **this is currently not documented, but will be in the future**
+
+  The dev portal is a key component of the Fusion Framework ecosystem, providing a user-friendly interface for developers to interact with their applications. It allows developers to easily manage and test their applications, providing a streamlined development experience.
+
+  The Dev Portal uses by default the `@equinor/fusion-framework-dev-portal` package, which is the official dev portal package provided by Fusion which is developer-friendly portal for developing and testing Fusion Framework applications. But it is possible to specify any package as a dev portal, allowing for customization of the development experience. This flexibility enables developers to create their own dev portals or use third-party solutions that better fit their needs.
+
+  The CLI now supports the `fusion-framework-cli auth login` command for authentication, which is a more secure and user-friendly way to manage access to Fusion Framework applications. This command simplifies the authentication process, making it easier for developers to log in and start working on their applications without needing to manually set environment variables or manage tokens. _`FUSION_TOKEN`_ is still supported for CI/CD and automation, but the CLI now provides a more streamlined and intuitive way to handle authentication.
+
+  The CLI has now been divided into three main groups:
+
+  - **bin**: This namespace contains executable functions that can be executed from node scripts, handy for automation and scripting or creating a custom CLI.
+  - **commands**: This namespace contains commands that can be executed from the CLI, providing a user-friendly interface for developers to interact with the Fusion Framework.
+  - **lib**: This namespace is reserved for consumers of the CLI, like defining configuration files, exposing interfaces, and other utilities that can be used in custom scripts or applications. This separation allows for better organization and modularity of the CLI codebase, making it easier to maintain and extend.
+
+  **BREAKING CHANGES:**
+
+  the `--service` flag has been removed since the CLI now uses the Fusion Framework internally, which does not require this flag, but uses service discovery to resolve endpoints automatically according to provided Fusion environment variables. This change simplifies the CLI usage and aligns it more closely with the Fusion Framework's architecture, allowing for a more seamless integration and improved developer experience.
+
+  All `app -build-???` has alias to correct commands, but been flagged as deprecated and will be removed in the next major version.
+
+### Minor Changes
+
+- [#3074](https://github.com/equinor/fusion-framework/pull/3074) [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13) Thanks [@odinr](https://github.com/odinr)! - Added CLI, bin and lib functionality to the Fusion Framework CLI for portal development and management.
+
+### Patch Changes
+
+- [#3074](https://github.com/equinor/fusion-framework/pull/3074) [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13) Thanks [@odinr](https://github.com/odinr)! - update Vite to 6.3.5
+
+- Updated dependencies [[`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13), [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13), [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13), [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13)]:
+  - @equinor/fusion-framework-dev-server@1.0.0-next.0
+  - @equinor/fusion-framework-dev-portal@1.0.0-next.0
 
 ## 10.7.4
 

package/README.md

@@ -1,42 +1,169 @@
 ---
 title: Fusion Framework CLI
+description: >
+  Fusion Framework CLI is a powerful tool for developing, building, and publishing applications and portal templates within the Fusion Framework ecosystem. See the documentation for full guides, configuration, and advanced usage.
+tags: 
+  - fusion-framework
+  - cli
+  - app-development
+  - portal-development
+  - dev-server
+  - ci-cd
+  - authentication
+  - configuration
+  - manifest
+  - registry
+  - publishing
+  - service-discovery
+  - equinor
+  - documentation
+  - getting-started
+keywords:
+  - fusion framework
+  - cli
+  - app development
+  - portal development
+  - dev server
+  - authentication
+  - ci/cd
+  - configuration
+  - manifest
+  - publishing
+  - registry
+  - service discovery
 ---
 
-### fusion-framework-cli
+# Fusion Framework CLI
 
-The cli, named `fusion-framework-cli`, contains tooling for running, building and publishing your application.
+[![npm version](https://img.shields.io/npm/v/@equinor/fusion-framework-cli.svg?style=flat)](https://www.npmjs.com/package/@equinor/fusion-framework-cli)
+[![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](./LICENSE)
 
-The fusion-famework-cli should be installed as a devDependency.
+---
+
+## Table of Contents
+
+- [Fusion Framework CLI](#fusion-framework-cli)
+  - [Table of Contents](#table-of-contents)
+  - [Overview](#overview)
+  - [Features \& Benefits](#features--benefits)
+  - [Getting Started](#getting-started)
+    - [1. Install the CLI](#1-install-the-cli)
+    - [2. Initialize or update your app's manifest and config files](#2-initialize-or-update-your-apps-manifest-and-config-files)
+    - [3. Start the development server](#3-start-the-development-server)
+    - [4. Log in to the Fusion Framework (if needed)](#4-log-in-to-the-fusion-framework-if-needed)
+    - [5. Build and publish your app](#5-build-and-publish-your-app)
+    - [6. Upload configuration](#6-upload-configuration)
+  - [Common Commands](#common-commands)
+  - [Example: package.json](#example-packagejson)
+  - [Troubleshooting](#troubleshooting)
+  - [Documentation](#documentation)
+  - [Contributing](#contributing)
+  - [Tooling Roadmap](#tooling-roadmap)
+
+## Overview
+
+Fusion Framework CLI is a command-line tool for developing, building, and publishing applications and portal templates within the Fusion Framework ecosystem. It streamlines workflows, automates common tasks, and supports modern CI/CD pipelines.
+
+## Features & Benefits
+
+- **Unified developer experience**: One tool for development, build, and deployment.
+- **Rapid local development**: Hot reload and fast feedback.
+- **Environment-specific configuration**: Manage manifests and configs per environment.
+- **Integrated authentication**: Secure your apps locally and in CI/CD pipelines.
+- **Service discovery**: Built-in support for Fusion services.
+- **Extensible architecture**: Widgets, portals, and more coming soon.
+- **Comprehensive documentation**: Migration guides, app/portal setup, and troubleshooting.
+
+## Getting Started
+
+### 1. Install the CLI
 
 ```sh
 pnpm add -D @equinor/fusion-framework-cli
 ```
 
-You can always use the option `-h or --help or help` to get help for the CLI and its commands.
+### 2. Initialize or update your app's manifest and config files
+
+See [Developing Apps](./docs/application.md) for manual setup and configuration guidance.
+
+### 3. Start the development server
+
+```sh
+pnpm fusion-framework-cli dev
+```
+
+### 4. Log in to the Fusion Framework (if needed)
+
+```sh
+pnpm fusion-framework-cli auth login
+```
+
+### 5. Build and publish your app
+
+```sh
+pnpm fusion-framework-cli publish --env <environment>
+```
 
-Example:
+### 6. Upload configuration
 
 ```sh
-fusion-framework-cli help
+pnpm fusion-framework-cli app config --upload --env <environment>
+```
+
+> **Tip:** For CI/CD and automation, set the `FUSION_TOKEN` environment variable. See [Authentication](./docs/auth.md) for details.
+
+## Common Commands
+
+| Command                                | Description                          |
+| -------------------------------------- | ------------------------------------ |
+| `pnpm fusion-framework-cli dev`        | Start local development server       |
+| `pnpm fusion-framework-cli auth login` | Authenticate with Fusion             |
+| `pnpm fusion-framework-cli app ...`    | Working with Fusion applications     |
+| `pnpm fusion-framework-cli portal ...` | Working with Fusion portal templates |
+
+## Example: package.json
+
+A minimal example for a Fusion Framework app:
+
+```json
+{
+  "name": "@equinor/fusion-framework-app",
+  "version": "0.0.0",
+  "description": "Fusion Framework App",
+  "main": "dist/index.js",
+  "files": [
+    "path-to-some-file/foo.png"
+  ]
+}
 ```
 
-### App Commands
+> **Note:** The `main` field should point to the build output (e.g., `dist/index.js`).
+
+## Troubleshooting
 
-See [App Commands](/cli/docs/commands.md)
+If you encounter errors like `libsecret-1.so.0: cannot open shared object file`, it means `libsecret` is missing. see the [libsecret installation guide](./docs/libsecret.md) for instructions on how to install it based on your operating system.
 
-### Configuration
+- **Command not found?** Ensure your `node_modules/.bin` is in your PATH or use `pnpm`/`npx`.
+- **Authentication issues?** See [Authentication](./docs/auth.md) for troubleshooting tokens and login.
+- **Build errors?** Check your app's manifest and config files for typos or missing fields.
+- **Need help?** Open an issue or see the [docs folder](./docs/).
 
-See [Configuration](/cli/docs/configuration.md)
+## Documentation
 
-### Tooling
+- [Migration Guide: v10 to v11](./docs/migration-v10-to-v11.md): Learn about breaking changes and how to upgrade.
+- [Developing Apps](./docs/application.md): Step-by-step guide to building and configuring apps.
+- [Developing Portals](./docs/portal.md): Guide to building, configuring, and publishing portal templates.
+- [Authentication](./docs/auth.md): Setting up authentication for local and CI/CD environments.
+- For more guides and advanced topics, see the [docs folder](./docs/).
 
-- tooling for [Vitest](https://vitest.dev/) - 🚀 coming soon
-- tooling for proxy configuration  - 🚀 coming soon
+## Contributing
 
-### Widget
+We welcome contributions! See our [contributing guide](../../contributing/development.md) for details on how to get started, coding standards, and submitting pull requests.
 
-Tooling for developing widgets  - 🚀 coming soon
+## Tooling Roadmap
+
+- **Vitest integration** (coming soon)
+---
 
-### Portal
+For more information, visit the [docs folder](./docs/) or open an issue for support.
 
-Tooling for developing portals  - 🚀 coming

package/bin/build/bin.js

@@ -0,0 +1,21 @@
+export { b as buildApplication, c as buildPortal, a as bundleApp, d as bundlePortal, g as generateApplicationConfig, l as loadPortalManifest, e as pack, p as publishAppConfig, s as startAppDevServer } from './portal-pack-CAsnV44B.js';
+import 'vite';
+import 'chalk';
+import '@azure/msal-node';
+import 'open';
+import 'node:http';
+import 'node:url';
+import 'zod';
+import 'is-ci';
+import '@equinor/fusion-imports';
+import 'lodash.mergewith';
+import '@equinor/fusion-framework-dev-server';
+import 'node:fs';
+import 'node:fs/promises';
+import 'node:path';
+import 'read-package-up';
+import 'node:assert';
+import 'node:child_process';
+import 'adm-zip';
+import 'pretty-bytes';
+import 'ora';