[IGN-11534] 8.3 Web UI - Exposure of Internal UI Components

Ignition 8.3 Early Access
1

Hello,

While working on refactoring the configuration interfaces for our modules, I've taken a close look at the new configuration pages introduced in Ignition 8.3 and their implementation in React.

I noticed that some components — very useful for building configuration pages — are actively used internally (as seen in the 8.3 bundles), but are not publicly exposed via the @inductiveautomation/ignition-web-ui package. In particular:

  • ResourceModeSingletonPage
  • PasswordInput
  • (and other similar building blocks)

These components clearly exist in the 8.3 source and are used in official pages like GatewaySettingsPage, yet they aren’t currently available to third-party module developers via public exports.

My questions are:

  • Are these components planned to be exposed in the near future?
  • Is there an intention to open them up as part of a public API (via @inductiveautomation/ignition-web-ui or another package)? Maybe expose @inductiveautomation/ignition-gateway-lib ?
  • Is it recommended to rebuild these components ourselves at this stage?
  • Or would it be better to wait for an official exposure?
  • Is the ignition-web-ui library mature enough today to justify migrating our custom configuration pages to it?

I’d like to:

  • Avoid duplicating or rewriting components that already exist and work well,
  • Stay aligned with the UX/UI patterns used by Ignition 8.3 for a consistent user experience,
  • Preserve long-term maintainability (avoiding divergence, unnecessary wrappers, or technical debt).

Any visibility into the roadmap for SDK/UI components would be greatly appreciated in order to make an informed decision about migrating our modules.

8 Likes
2

I hope too IA will provide a solution with some boilerplate code for this common use case like it was in 8.1 :crossed_fingers:

2 Likes
3

Hi @e.sagnelonge,

I don’t have the answers to your questions at the moment, but they are under the team’s radar. We are planning to discuss this internally, so stay tuned!

2 Likes
4

Still dreaming of @inductiveautomation/ignition-gateway-lib every night… :eyes:

1 Like
5

Hi all,
I have this question as well. IgnitionGatewayLib.js.map is included in the public gateway-api-web-8.3.X.jar bundles, but is mapped to the Babelified source, as opposed to the original. This has the effect of completely revealing the inner workings of the library to the public, but in a format that's super annoying.

Since the post-Babel sourcemaps are already public, is there any chance that IA could provide the fully-linked sourcemaps for @inductiveautomation/ignition-gateway-lib? If not, could we receive some guidance regarding the questions posed by @e.sagnelonge?

Thanks everyone.