Skip to content

Conversation

@JohnC-80
Copy link
Contributor

@JohnC-80 JohnC-80 commented Jan 14, 2026

With this update, we shift the POC code to conform to current stripes-cli API.
The build commands build to an output directory by default.

At the workspace level with stripes-core, stripes-connect, stripes-components: (assuming that's where the config file is)

Build a module-federation host app:

yarn stripes build --federate stripes.config.js

Serve the host app (dev mode)

yarn stripes serve --federate stripes.config.js

At the ui-module level (Builds module bundle for static hosting)

yarn stripes build --federate

Serving the federated ui-module (dev mode)

yarn stripes serve --federate

Some server features have been updated for sake of serving the host app so that it can further be loaded into a separately hosted 'hub'.

@JohnC-80 JohnC-80 requested a review from a team as a code owner January 14, 2026 15:35
@github-actions
Copy link

github-actions bot commented Jan 14, 2026

Jest Unit Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit a2a227e. ± Comparison against base commit ff0c0ca.

♻️ This comment has been updated with latest results.

@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
1 Security Hotspot
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

])
.positional('configFile', stripesConfigFile.configFile)
.option('federate', {
describe: 'At platform level, serves an empty host platform, using configured entitlementUrl to procure a list or remote apps. At the module level, this registers/serves the app as a locally federated remote.',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typos: "At THE platform...", "a list OF..."

"At the platform level": it also spins up a local registry, right? Should we say that?

function start(dir, options) {
const app = express();
app.use(express.json());
app.use(cors());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wide-open cors() makes Sonar grumpy. Do we think Sonar is correct here and we should limit dev-stuff to localhost, or do we want to leave it wide-open, knowing that it's insecure from some points of view but ack'ing that this is how things go during development when we don't have all those configurations ironed out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants