@xterm/addon-ligatures@0.10.0: missing lib/addon-ligatures.js (only .mjs shipped)

[dubynam]

Bug

@xterm/addon-ligatures@0.10.0 ships only the ESM build (lib/addon-ligatures.mjs) but package.json declares "main": "lib/addon-ligatures.js". The CJS/UMD build (lib/addon-ligatures.js) is absent from the published package.

Impact

Any host app using an AMD/CommonJS loader to load the addon by its main entry will get ERR_FILE_NOT_FOUND and silently fail to activate ligatures, even when the user has correctly configured terminal.integrated.fontLigatures.enabled.

package.json (installed)

{
  "name": "@xterm/addon-ligatures",
  "version": "0.10.0",
  "main": "lib/addon-ligatures.js",
  "module": "lib/addon-ligatures.mjs"
}

Actual lib/ contents

lib/addon-ligatures.mjs       ✅ present
lib/addon-ligatures.mjs.map   ✅ present
lib/addon-ligatures.js        ❌ MISSING

Workaround applied

Manually created lib/addon-ligatures.js by wrapping .mjs body (which has no top-level import statements) in a UMD shim:

!function(e,t){
  "object"==typeof exports&&"object"==typeof module?module.exports=t():
  "function"==typeof define&&define.amd?define([],t):
  e.LigaturesAddon=t().LigaturesAddon
}(globalThis,(()=>{
  // ...mjs body with export{Es as LigaturesAddon} removed...
  return {LigaturesAddon: Es};
}));

Steps to reproduce

1. Install @xterm/addon-ligatures@0.10.0
2. Attempt to require('@xterm/addon-ligatures/lib/addon-ligatures.js') or load it via AMD
3. Error: Cannot find module / ERR_FILE_NOT_FOUND

Environment

• @xterm/addon-ligatures version: 0.10.0
• Host: Antigravity (Google IDE, Electron-based, AMD loader)
• OS: macOS

[savetheclocktower]

Yeah, this is complicating an attempted upgrade of @xterm/xterm from v5 to v6 in my project because the only versions of @xterm/addon-ligatures that state compatibility with @xterm/xterm v6 are all affected by this issue.

My target is a CommonJS-only environment, so my Rollup config will automatically transpile any packages that are ESM-only… but will treat as external any packages that claim to have a CommonJS bundle. So this is the worst of both worlds — declaring CommonJS support, but pointing to a .js file that doesn't exist. I was able to work around it with special logic in my rollup.config.mjs that manually makes this package resolve to the proper path and forces Rollup to realize it needs to transpile this package to CommonJS.

All the other addons I use still ship a CommonJS version, so I can only assume that one is intended to exist for this plugin and its absence is just an oversight.