UniverJS events and methods missing after Angular production build (CellPointerDown, setNumberFormat, etc.)

[Yosra-Sassi]

Hi UniverJS team,

First, thank you for this amazing library — it's very powerful and well-designed.

🔴 Problem

I’m developing an Angular application using UniverJS (v0.9.2) to provide Excel-like features. Everything works perfectly in development (localhost).

However, once I build the app for production, I lose access to some critical methods and event constants on the UniverJS API objects.

🟢 Expected Behavior

The available API objects and their properties (like Event.CellPointerDown and range.setNumberFormat) should be identical between development and production builds.

❌ Actual Behavior

• univerAPI.Event loses many event properties in production (like CellPointerDown, CellPointerMove, etc.)

• Calling range.setNumberFormat(...) in production throws:

  range.setNumberFormat is not a function

• This only happens in the production build, not during development.

Plugin Registration Code

Here is the code I use to initialize and register all the UniverJS plugins:

private registerCorePlugins(containerId: string): void {
  this.univer.registerPlugin(UniverRenderEnginePlugin);
  this.univer.registerPlugin(UniverUIPlugin, { container: containerId });
  this.univer.registerPlugin(UniverFormulaEnginePlugin);
  this.univer.registerPlugin(UniverDocsPlugin, { hasScroll: false });
  this.univer.registerPlugin(UniverDocsUIPlugin);
  this.univer.registerPlugin(UniverSheetsPlugin);
  this.univer.registerPlugin(UniverSheetsUIPlugin);
  this.univer.registerPlugin(UniverSheetsFormulaPlugin);
  this.univer.registerPlugin(UniverSheetsFormulaUIPlugin);
  this.univer.registerPlugin(UniverSheetsNumfmtPlugin);
  this.univer.registerPlugin(UniverSheetsNumfmtUIPlugin);
  this.univer.registerPlugin(UniverSheetsDataValidationPlugin);
  this.univer.registerPlugin(UniverSheetsDataValidationUIPlugin);
}

🛠️ Angular Build Configuration

Here’s the relevant part of my angular.json used to prevent aggressive optimization:

"build": {
  "builder": "@angular-devkit/build-angular:application",
  "options": {
    "outputPath": "dist/webSolveoFrontend",
    "index": "src/index.html",
    "browser": "src/main.ts",
    "polyfills": ["zone.js"],
    "tsConfig": "tsconfig.app.json",
    "assets": [
      "src/favicon.ico",
      "src/assets",
      {
        "glob": "**/*",
        "input": "public",
        "output": "/"
      }
    ],
    "styles": [
      "@angular/material/prebuilt-themes/azure-blue.css",
      "src/styles.css",
      "node_modules/@univerjs/presets/lib/styles/preset-sheets-core.css"
    ],
    "scripts": [],
    "allowedCommonJsDependencies": [
      "@univerjs/core",
      "@univerjs/sheets",
      "@univerjs/sheets-ui",
      "@univerjs/presets"
    ]
  },
  "configurations": {
    "production": {
      "optimization": {
        "scripts": false,
        "styles": true
      },
      "outputHashing": "all",
      "budgets": [
        {
          "type": "initial",
          "maximumWarning": "20mb",
          "maximumError": "30mb"
        },
        {
          "type": "anyComponentStyle",
          "maximumWarning": "4kB",
          "maximumError": "8kB"
        }
      ]
    },
    "development": {
      "optimization": false,
      "extractLicenses": false,
      "sourceMap": true
    }
  },
  "defaultConfiguration": "production"
}

🟢 Development (full event list)

🔴 Production (missing events)

🙏 Request for Help

Has anyone experienced a similar issue when deploying an Angular app with UniverJS?

Any ideas on how to ensure that the required events and APIs are preserved in the production build?

Thank you very much in advance 🙌

[jikkai]

If you’re using Univer via the plugin mode, you’ll need to manually import the required facade package to access the corresponding facade APIs.

For example, the FRange.setNumberFormat method you mentioned is provided by the @univerjs/sheets-numfmt/facade package.

import { FUniver } from '@univerjs/core/facade'

import '@univerjs/sheets-numfmt/facade'

// ...

You can refer to the documentation here: https://docs.univer.ai/guides/sheets/getting-started/facade#integrating-facade-api-in-plugin-mode.

Since the information you provided consists only of code snippets and not a fully functional minimal reproducible example, I cannot confidently determine the root cause of the issue. If you need further assistance, please follow the community guidelines to provide a minimal reproducible demo.