Cairn
NousResearch/hermes-agent

TUI package ESM module metadata bundling fixes

Cluster 38304 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 2 PRs.

These issues and PRs concern missing or incorrect ESM module markers and metadata in the TUI wheel/bundle, causing Node.js import errors and MODULE_TYPELESS_PACKAGE_JSON warnings. The work involves shipping proper package.json metadata and ESM markers with the bundled distribution.

Open issues0

No open issues.

Open PRs2

  • PR#38318fix(tui): ship bundled module metadata
  • PR#40037fix(tui): mark bundled entry as esm

1 PR closed without merging

From the close comments: other 1

  • #39822 fix(tui): ship ESM package marker in wheel bundle · other → #38318, #39805, #38304
Closed issues · 2
  • Closed#38304Packaged TUI dist lacks module metadata, causing MODULE_TYPELESS_PACKAGE_JSON warning
  • Closed#39805TUI bundled entry.js fails on Node.js v18: Cannot use import statement outside a module
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.44: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/38304.json
cluster/38304.md