fusion-cli

library2.39.1jsnpmunverified

The `fusion-cli` is the command-line interface for the Fusion.js framework, designed to orchestrate the development lifecycle of universal React applications. It handles compile-time configurations for both server and browser bundles, facilitating development, testing, and production deployments. Key features include a standardized Babel configuration with modern ECMAScript support, efficient hot module reloading, and an integrated web server. Fusion.js, originally developed by Uber, focuses on high performance, server-side rendering (SSR), and a modular, plugin-driven architecture, enabling seamless transitions between client and server logic. As of the provided npm data, the current version is 2.39.1. However, the last recorded release in the excerpt is from October 2022, and the broader Fusion.js project on GitHub shows minimal recent activity, suggesting a slow or halted development cadence for the framework. It emphasizes a strict, opinionated build process, notably not supporting custom Webpack configurations to maintain internal consistency and facilitate future bundler transitions.

web-framework devops

npm install fusion-cli

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · FUSION-CLI

fusion-cli

web-frameworkjavascriptv2.39.1

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

App

✓ import App from 'fusion-react'

✗ import { App } from 'fusion-react'

The primary class for instantiating a Fusion.js application, typically a default export from 'fusion-react'.

createPlugin

✓ import { createPlugin } from 'fusion-core'

✗ import createPlugin from 'fusion-core'

Function used to define and create Fusion.js plugins, a named export from 'fusion-core'.

Router

✓ import Router from 'fusion-plugin-react-router'

✗ import { Router } from 'fusion-plugin-react-router'

A common plugin for routing in Fusion.js applications, typically a default export.

This quickstart demonstrates the core structure of a Fusion.js application using `fusion-cli`, showing app initialization, plugin registration, and a basic custom plugin.

import React from 'react'; import App from 'fusion-react'; import {createPlugin} from 'fusion-core'; import Router from 'fusion-plugin-react-router'; import {SessionToken} from 'fusion-tokens'; import JWTSession from 'fusion-plugin-jwt'; // Define a simple root component const Root = () => <div>Hello Fusion.js!</div>; // Create and export the Fusion.js app export default () => { const app = new App(<Root />); // Register common plugins like Router and Session app.register(Router); app.register(SessionToken, JWTSession); // Example of a custom plugin logging requests const MyPlugin = createPlugin({ provides() { return { logMessage: (message) => console.log(`MyPlugin: ${message}`), }; }, middleware(deps, middleware) { return async (ctx, next) => { deps.logMessage(`Request received for path: ${ctx.path}`); await next(); }; }, }); app.register(MyPlugin); return app; };

fusion --version

Debug

Known issues

breakingFusion.js, and by extension `fusion-cli`, does not support custom `webpack.config` files. This is a deliberate design choice to maintain consistency and allow the framework to evolve its internal bundling mechanisms. Any attempts to provide a custom Webpack configuration will be ignored or lead to unexpected behavior.

fix

Instead of custom Webpack configurations, leverage Fusion.js's plugin architecture and `.fusionrc.js` for build-time customizations. If a feature is truly missing, consider contributing to the Fusion.js project or creating a feature request.

affects: >=2.0.0

deprecatedThe `--testFolder` CLI option is deprecated. Developers should migrate to using `--testMatch` or `--testRegex` for specifying test file locations.

fix

Replace `--testFolder <path>` with `--testMatch '<glob-pattern>'` or `--testRegex '<regexp-string>'` in your `package.json` scripts or CLI commands.

affects: >=2.34.0

gotchaWhen running Fusion.js applications, the `fusion dev` command builds browser artifacts in memory and does not save them to the filesystem. In contrast, `fusion build` saves artifacts to disk. If you intend to run a previously built application using `fusion start`, you *must* use `fusion build` first; running `fusion start` after `fusion dev` will fail due to missing build artifacts.

fix

Always use `yarn fusion build` or `npx fusion build` before `yarn fusion start` for production or staging environments. `yarn fusion dev` is for development with Hot Module Reloading.

affects: >=2.0.0

breakingFusion.js CLI version 2.35.0 updated the React dependency to 18.2.0. Applications using older React versions might encounter compatibility issues or require updates to React-related packages and code patterns to align with React 18's changes (e.g., `createRoot`).

fix

Ensure your application and all Fusion.js-related plugins are compatible with React 18. Update `react` and `react-dom` peer dependencies accordingly. Review React 18 upgrade guides for potential breaking changes in your application code.

affects: >=2.35.0

gotchaThe `fusion-cli` infers the `NODE_ENV` environment variable from the initiating CLI command and its flags. It cannot be manually configured through environment variables directly and attempts to override it may be ignored or lead to unexpected build outcomes.

fix

Rely on the CLI commands (e.g., `fusion dev`, `fusion build --production`) to set the appropriate `NODE_ENV`. If specific build behaviors depend on `NODE_ENV`, ensure they are configured within the `.fusionrc.js` or via plugin options that respond to the CLI-inferred environment.

affects: >=2.0.0

Errors

Common errors & fixes

No command given. Type 'fusion help' for more information.

The `fusion` command was executed without specifying a subcommand (e.g., `dev`, `build`, `start`).

fix

Run `fusion <command>` where `<command>` is one of the available subcommands like `fusion dev`, `fusion build`, or `fusion start`. You can see all available commands with `fusion help`.

Cannot read property 'sub' of undefined

This error, often seen in Fusion.js applications, typically indicates an issue with a plugin trying to access a property on an undefined object, frequently within context (`ctx`) or a plugin's dependency (`deps`). It suggests a missing dependency, incorrect plugin registration, or an unexpected state in the application context.

fix

Verify that all required plugins are correctly registered using `app.register()` in your `src/main.js` or similar entry point. Inspect the stack trace to identify the problematic plugin and ensure its dependencies are satisfied. Check for proper initialization of values within the plugin's `provides` method.

Fresh install not working / Unable to install dependencies from fresh clone of master

These generic errors often point to issues with package manager versions (Yarn/npm), Node.js version incompatibilities, or underlying build tool problems (like `iltorb` module deprecation as seen in some issues). Fusion.js is a monorepo that historically used Yarn v2 (now Yarn Berry).

fix

Ensure your Node.js, Yarn, and npm versions meet the `engines` requirements. For Fusion.js projects, ensure you are using the correct Yarn version (historically Yarn v2/Berry) and have run `yarn install` at the monorepo root. Address any specific dependency installation errors.

Build completed (printed twice)

A known issue where the build completion message is redundantly printed twice in the console output.

fix

This is a minor aesthetic issue and does not generally impact the build process or output. No direct fix for users, as it's an internal CLI behavior.

Upgrade

Version history

2.39.1latest on npm

Audit

Dependencies

fusion-corerequiredCore dependency for the Fusion.js framework.

reactrequiredPrimary UI library for Fusion.js applications.

react-domrequiredDOM renderer for React applications.

enzymeoptionalTesting utility for React components.

graphqloptionalOften used for data fetching with plugins like fusion-plugin-apollo.

Agent activity

2 hits · last 30 days

node

Resources

githubhttps://github.com/fusionjs/fusionjs ↗

packagehttps://www.npmjs.com/package/fusion-cli ↗

homepagehttps://fusionjs.com ↗