NITRO wrapper unusable: Broken in-memory & HTTP source paths in @mieweb/ui (Two critical bugs)

[wreiske]

Summary

The NITRO datavis wrapper in @mieweb/ui is currently broken and unusable for both its in-memory and HTTP source paths. This makes it impossible to adopt NITRO in the current state, which is forcing downstream consumers to use AG Grid instead of NITRO.

Context & Reasoning

Refer to the attached screenshots for additional detail:

Key points from developer investigation:

• The wrapper is broken for both in-memory sources and HTTP source paths.
• This is not a minor or fit-and-finish issue. They are two real bugs that prevent the use of NITRO in this repo.
• The problems surfaced when trying to use datavis-ace@4.0.0-PRE.1, where type imports and runtime behavior did not work (datavis/src/... import specifier issues, missing LocalSource and varName).
• AG Grid was adopted instead, but the goal is to restore NITRO functionality so it can be used going forward.
• Suggestions:
  • Fix the import specifiers and in-memory/HTTP handling in the NITRO wrapper in this repo.
  • After fixes, validate NITRO end-to-end for both source types so it can become the default again.

Impact

• Product unable to use NITRO as intended.
• Brand theming and deployment already done on AGGrid, but it's a workaround, not a solution.

Steps to Reproduce

1. Install and attempt to use NITRO/datavis-ace@4.0.0-PRE.1 via @mieweb/ui in a consuming project.
2. Observe the type import errors and runtime failures for both source types.

Attachments

See screenshots above.

---

Please prioritize fixing the NITRO wrapper’s import specifiers, source path handling, and missing types.

CC: anyone trying to use NITRO grids in @mieweb/ui right now.

[tvenable-mie]

Thanks for filing this. Before we dig in, the issue as written is missing some key details that would help us triage and fix it efficiently:

1. Steps to reproduce. "Install and attempt to use NITRO" is too broad. Consumers shouldn't need to interact with datavis-ace directly — they just use the components from @mieweb/ui, e.g.:

   <DataVisNitroSource type="http" url="/sample-data.json">
     <DataVisNitroGrid
       title="Auto Derived Columns"
       showControls
       height="480px"
     />
   </DataVisNitroSource>

   What exactly are you rendering, with what props, and in what context? A minimal reproduction would go a long way.

2. Error messages. The issue references "type import errors and runtime failures" but doesn't include any actual error output — no stack traces, no TypeScript compiler errors, no console logs. "See screenshots above" points to a chat conversation, not to error output from a build or runtime. Please paste the exact errors you're seeing.

3. Expected vs. actual behavior. What specifically should happen when the wrapper is working correctly, and what happens instead? For example: "I expect <DataVisNitroSource> with an HTTP URL to render a grid, but instead I get [specific error / blank screen / crash]."

Without these details it's difficult to distinguish between a bug in the wrapper, a configuration issue, or a usage issue in the consuming project. Could you update the issue with:

• A minimal code snippet that reproduces the problem
• The exact error messages (terminal, browser console, or TS compiler output)
• The version of @mieweb/ui you're using
• Expected vs. actual behavior for each of the two bugs mentioned

That will let us prioritize and fix this much faster.

---

Here are a few places where it's being used that might help to feed into Copilot, it seems like the AI thinks that it needs to access datavis-ace directly, which it doesn't... the NITRO package does all that for you, and the React tags provided by ui should provide everything needed for basic usage. If there are gaps, please let me know specifically what you need. I hope this helps!

• Example usage in this project
• Example usage in E-Chart Sim

[garrity-miepub]

I grabbed the app and ran it locally. Looks like it was just missing the datavis dependencies.

Changes

• package.json — Added @mieweb/datavis, datavis-ace, i18next, and react-i18next dependencies
• vite.config.ts — Added datavis → @mieweb/datavis alias so @mieweb/ui/dist/datavis.js can resolve its datavis/src/... imports
• src/pages/DashboardPage.tsx — Replaced the AG Grid DataTable with DataVisNitroGrid + DataVisNitroContext.Provider, using a local window variable to feed the data

After that, I added the datavis component to the dashboard and it loaded without errors