Skip to content

Spike: modular React studio loading UI modules from NuGet packages #8839

Open

Description

@elsa-workflows-bot

Part of the React studio preview (3.11) epic.

Size: M (~3 working days)
Depends on: none

Goal

Prove the module architecture before the port: an ASP.NET Core host + SDK v0 (routes, navigation, UI-hint editor slots) + import map, an in-box Labels module and a third-party sample module consumed only as a .nupkg from a local feed.

Acceptance criteria

  • Both modules load from packed .nupkg files; the third-party one has no project reference to the host
  • Exactly one React instance at runtime (shared context such as query client and theme works across modules)
  • The manifest endpoint lists only modules whose CShells feature is enabled
  • A module with an incompatible host/SDK major is rejected with a visible diagnostic; the shell still works
  • Asset URLs carry the package version (cache-busting)
  • Vite HMR dev loop works through the host; a CSP with a nonce works with the import map
  • A Playwright smoke test passes; go/no-go is recorded in the ADR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:studioQuality loop area: studiocoreThis issue relates to the core libraryelsa 3This issue is specific to Elsa 3prio highIs on the roadmap for the near-futuretriaged

    Type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions