@mieweb/ui/datavis (NITRO grid) imports an unpublished `datavis` package — subpath unbuildable

[horner]

@mieweb/ui/datavis (NITRO grid) is unusable — imports an unpublished datavis package

Summary

The NITRO grid exported from the @mieweb/ui/datavis subpath cannot be built by
consumers. Its compiled bundle (dist/datavis.js) imports modules from a bare
datavis package that is not declared as a dependency and is not published
to any registry. Installing the one declared peer (datavis-ace) is not
sufficient.

• Affected version: @mieweb/ui@0.6.1
• Affected export: @mieweb/ui/datavis (DataVisNitroGrid, DataVisNitroSource)

Details

dist/datavis.js resolves two distinct packages:

Import specifier	Provides	Status
datavis-ace (Source, ComputedView)	data/compute engine	Declared as an optional peer dep (datavis-ace@4.0.0-PRE.2); published to npm; installable
datavis/src/components/DataGrid, datavis/src/adapters/*, datavis/src/components/table/TableRenderer	the actual grid React UI	Not in peerDependencies/dependencies; not resolvable

The published datavis-ace@4.0.0-PRE.2 tarball contains only the engine (34
files, src/**/*.js) — no React components, no DataGrid/TableRenderer. So
the grid UI imports remain unresolved even after installing it.

The datavis React-component package is not available under any public name we
could find:

• datavis → resolves to an unrelated legacy 1.0.0 package (HTML/CSS + vim
  swap files), not these components.
• @mieweb/datavis, @mieweb/datavis-react, datavis-react, @datavis/react
  → all 404.

Reproduction

npm install @mieweb/ui@0.6.1 datavis-ace@4.0.0-PRE.2

// Any module that pulls in the NITRO grid:
import { DataVisNitroGrid, DataVisNitroSource } from '@mieweb/ui/datavis';

A production build (Vite/Rollup/webpack) fails to resolve
datavis/src/components/DataGrid (and the sibling datavis/src/... imports).

node -e "require.resolve('datavis/src/components/DataGrid')"
# Error: Cannot find module 'datavis/src/components/DataGrid' (MODULE_NOT_FOUND)

Secondary issue: local-data API is not surfaced

Even if the package resolved, DataVisNitroSource type="local" exposes no
declarative data prop. It constructs new Source({ type: 'local' }) and a
ComputedView, then provides them via React context. Feeding an in-memory array
appears to require imperative datavis-ace Source/ComputedView calls that
@mieweb/ui does not re-export or document. Please document (or add a data
prop / rows convenience) for the common "render a local array" case.

Suggested fixes (any one unblocks consumers)

1. Bundle the datavis/src/... component sources into dist/datavis.js so
   the subpath has no external bare datavis import.
2. Publish the datavis React-component package and declare it as a
   (peer) dependency of @mieweb/ui, with an accurate version range.
3. Document the required install set and the local-data loading API for the
   NITRO grid.

[horner]

This is what I asked Opus 6.8 to do on https://github.com/mieweb/opensource-server

Doug: Add nitro table support

Adding NITRO is blocked by a packaging problem in the published @mieweb/ui@0.6.1 — not something I can fix from our side. Here's what I verified:

The NITRO grid has a missing dependency that isn't on npm.

@mieweb/ui/datavis (the DataVisNitroGrid) bundle imports from two packages:

Import	Status
datavis-ace@4.0.0-PRE.2 (the data engine: Source, ComputedView)	✅ on npm, installable — but only 34 files, no React components
datavis/src/components/DataGrid, datavis/src/adapters/*, datavis/src/components/table/TableRenderer (the actual grid UI)	❌ not resolvable

The datavis React-component package is:

• Not declared in @mieweb/ui's peerDependencies (only datavis-ace is).
• Not published under any public name — I checked datavis, @mieweb/datavis, @mieweb/datavis-react, datavis-react, @datavis/react (all 404 except the public datavis@1.0.0, which is an unrelated legacy HTML/CSS package with vim swap files, not mieweb's components).

So a production build importing @mieweb/ui/datavis will fail to resolve datavis/src/components/DataGrid. There's no way to satisfy that import from the public registry. On top of that, the local DataVisNitroSource type="local" exposes no declarative data prop — feeding our array would require imperative datavis-ace Source calls that @mieweb/ui doesn't surface.

Conclusion: NITRO can't be wired up until @mieweb/ui either bundles datavis into its datavis.js output or publishes the datavis component package and declares it as a dependency. That's an upstream fix.