Next

[odinr]

Why

This PR introduces a collection of updates, enhancements, and fixes across the Fusion Framework monorepo. It includes refactors, dependency upgrades, bug fixes, documentation updates, and feature releases for multiple packages.

The current behavior includes outdated dependencies, limited functionality in some modules, and missing documentation for certain integrations.

@equinor/fusion-framework-cli

• The Fusion Framework CLI has been completely rewritten to use the Fusion Framework internally, reducing dependencies and improving performance. This rewrite makes the CLI a first-class citizen in the Fusion Framework ecosystem, providing a more consistent and integrated experience.

• The Dev Portal has been modularized and moved to a separate package, @equinor/fusion-framework-dev-server, enabling a modular architecture and independent updates. The Dev Portal now supports live previews and API mocking, configurable via dev-server.config.js.

• The CLI's command structure has been reorganized into three main groups: bin (executable functions), commands (CLI commands), and lib (for consumers, config, and utilities). This improves organization and modularity.

• The --service flag has been removed, and the CLI now uses service discovery via Fusion environment variables. Additionally, all app -build-??? commands have been deprecated and will be removed in the next major version.

• Vite configuration and dev server functionality have been abstracted into the @equinor/fusion-framework-dev-server package. The CLI now provides a higher-level API that handles Vite configuration internally, while still allowing for customization through configuration options.

• New utility functions have been added to the CLI, including modules for resolving CI/CD metadata (e.g., GitHub Actions, Azure DevOps), git commit and remote info, and package metadata. These utilities support advanced scripting and automation scenarios.

• Support for portal configuration has been improved with new helpers for loading and resolving portal configuration files. The portal manifest has been refactored to use name and templateEntry for consistency with app manifests, and type safety and schema validation have been enhanced.

• The CLI has been modernized for ESM compatibility, including the use of deepmerge instead of lodash.mergewith, explicit .js extensions in imports, and updated package.json and tsconfig.json configurations.

• The dev server configuration has been refactored to improve merging logic, add a RecursivePartial type, and implement a custom array merge strategy. Documentation for configuration has also been improved.

• A Node.js version check has been added to the CLI entrypoint, recommending the use of the LTS version. Build configuration now injects version info via environment variables.

• The maintainability, type safety, and developer experience of the CLI and dev server packages have been significantly improved.

• For further details, see the CLI's README and the docs folder.

@equinor/fusion-framework-dev-portal

This PR introduces a new package, @equinor/fusion-framework-dev-portal, as part of a refactor of the @equinor/fusion-framework-cli.

Features

• Development portal for the Fusion framework
• Support for MSAL authentication
• Integration with service discovery
• Environment variable configuration

This package is a small part of the refactoring of the @equinor/fusion-framework-cli and while it can be used standalone, it is recommended to use the @equinor/fusion-framework-dev-server package for a more complete development experience.

Read More

For more detailed information, usage examples, and advanced configuration, please refer to the GitHub README for this package.

@equinor/fusion-framework-dev-server

Introduced a new package, @equinor/fusion-framework-dev-server, designed to provide a development server tailored for Fusion Framework applications. Built on top of Vite, it seamlessly integrates Vite and Fusion Framework configurations.

For more details, visit the GitHub repository.

Features

• createDevServer Function: Simplifies the creation of a development server using a configuration object.
• createDevServerConfig Function: Generates a Vite-compatible configuration for the development server.
• SPA Support: Includes spa.templateEnv for defining environment variables specific to Single Page Applications.
• API Service Discovery: Enables proxying and route mapping for API services via api.serviceDiscoveryUrl.
• Dynamic Proxy Routes: Introduced the processServices function to remap Fusion services' URIs and dynamically generate proxy routes.
• Logging: Integrated @equinor/fusion-log for customizable logging, with dedicated sub-loggers for SPA and API services.

Dependencies

The following dependencies were added to support the new package:

• @equinor/fusion-framework-vite-plugin-api-service
• @equinor/fusion-framework-vite-plugin-spa

@equinor/fusion-framework-module-http

• The HTTP module now uses the correct method acquireAccessToken from the auth provider to retrieve the access token for requests with scopes.
• This fixes compatibility with the new MSAL node module interface, which no longer exposes acquireToken but instead provides acquireAccessToken for token retrieval.
• Ensures the Authorization header is set correctly for authenticated HTTP requests.

@equinor/fusion-framework-module-msal-node

This release makes @equinor/fusion-framework-module-msal-node an explicit ESM package.

@equinor/fusion-framework-module-module

This release makes @equinor/fusion-framework-module an explicit ESM package.

@equinor/fusion-framework-react-components-people-provider

update @equinor/fusion-wc-person dependency to version 3.1.8

@equinor/fusion-framework-vite-plugin-api-service

Introducing a new Vite plugin for Fusion Framework applications that simplifies API development workflows through service discovery integration and API mocking.

Key capabilities:

• Proxy requests to backend services with automatic route generation
• Mock API responses for testing and development
• Intercept and transform API requests and responses
• Configure custom routes with middleware support

For complete documentation and examples, see the API Service Plugin README.

@equinor/fusion-framework-vite-plugin-spa

Introducing a powerful new Vite plugin for building Single Page Applications (SPAs) with the Fusion Framework and Vite. This plugin significantly streamlines the development workflow by automating HTML template generation, bootstrapping authentication and service discovery, and enabling seamless portal loading and API proxying.

Purpose:

This plugin represents a strategic modularization of the Fusion Framework CLI codebase. By extracting the SPA functionality into its own dedicated package, we've simplified the CLI's architecture while enabling greater flexibility. This modular design allows the SPA component to be replaced or reused by third-party developers independently of the CLI. The primary goal is to maintain a cleaner, more maintainable codebase through proper separation of concerns, with the CLI using this plugin rather than containing this functionality directly.

Key Features:

• Fusion Framework Bootstrap: Automatically initializes core modules and renders configured portals
• Service Discovery: Enables dynamic service routing and eliminates hardcoded service endpoints
• MSAL Authentication: Provides seamless Azure AD integration with configurable authentication flows
• Service Worker: Intercepts network requests to add authentication tokens and rewrite URLs for proxying
• Portal Integration: Loads and renders any portal by ID from local packages or the Fusion Portal Service
• Environment Configuration: Supports flexible configuration through code or .env files with proper naming conventions
• Custom Templates: Allows full control over HTML document structure while maintaining environment variable injection
• Custom Bootstrap: Supports advanced customization of the application initialization process
• API Service Integration: Works with @equinor/fusion-framework-vite-plugin-api-service for enhanced development capabilities

This plugin is designed for seamless integration with the Fusion Framework CLI and provides flexible configuration for both standard and advanced SPA scenarios.

@equinor/fusion-imports

Updated the files field in package.json to include both dist and src directories.

Bookmark

Refactored the Bookmark type to be an intersection of BookmarkWithoutData and an optional payload property, improving type safety and flexibility. Updated useBookmarkNavigate to use proper TypeScript typing for bookmark events.

Module Bookmark Changes:

• Refactored Bookmark type in packages/modules/bookmark/src/types.ts
• Added export for BookmarkProviderEvents type in packages/modules/bookmark/src/index.ts
• Updated JSDoc comment from @note to @remarks in packages/modules/bookmark/src/BookmarkClient.ts
• Reordered tsconfig references (event before services)

React Changes:

• Updated packages/react/modules/bookmark/src/portal/useBookmarkNavigate.ts to use proper TypeScript typing for bookmark provider events
• Removed React paths configuration from packages/react/app/tsconfig.json

Dependency Updates

• Vite: Upgraded to version 6.3.5 for improved performance and compatibility.
• Zod: Upgraded to the latest version to leverage new features and fixes.

Breaking changes

@equinor/fusion-framework-cli

• The --service flag has been removed. The CLI now uses service discovery via Fusion environment variables. All app -build-??? commands are deprecated and will be removed in the next major version. Migration Guide: v10 to v11

EsmNext to NodeNext

@equinor/fusion-framework-module and "@equinor/fusion-framework-module-msal-node is now built for module and moduleResolutionto NodeNext. This should not really effect any consumers, but all CJS will fail.

closes: #AB64518

---

Check off the following:

• Confirm that I checked changes to branch which I am merging into.

  • I have validated included files
  • My code does not generate new linting warnings
  • My PR is not a duplicate, check existing pr`s

• Confirm that the I have completed the self-review checklist.

• Confirm that my changes meet our code of conduct.

[changeset-bot]

🦋 Changeset detected

Latest commit: a86b21a

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Copilot]

Pull Request Overview

This PR performs a comprehensive modernization and refactoring of the Fusion Framework codebase, transitioning to ESM modules, updating dependencies, improving documentation, and adding new development tooling.

• Migration to ES modules with "type": "module" and .js extensions in imports
• Updated dependencies including Zod version bumps and TypeScript configuration improvements
• Enhanced documentation with comprehensive JSDoc comments and improved README files
• Introduction of new development server and portal packages for better development experience

Reviewed Changes

Copilot reviewed 224 out of 384 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
packages/modules/module/src/BaseConfigBuilder.ts	Updated imports to use .js extensions and improved JSDoc documentation
packages/modules/module/package.json	Added "type": "module" and version bump to support ESM
packages/modules/http/src/module.ts	Updated authentication method call from acquireToken to acquireAccessToken
packages/modules/http/package.json	Updated Zod dependency to version 3.25.76
packages/modules/event/src/event.ts	Replaced @note with @remarks in JSDoc comments
packages/modules/context/src/*	Extensive documentation improvements and type safety enhancements
packages/dev-server/src/*	New development server package with comprehensive configuration options
packages/dev-portal/src/*	New development portal package for local development
packages/cli/src/*	Major refactoring with improved utilities and type definitions

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}