fixing workbench deployement

[nabeelmd-eGov]

Summary by CodeRabbit

• Refactor
  • Updated the webpack production configuration for the workbench module, including changes to the entry point and module federation settings for improved identification and loading.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates focus on renaming elements within the webpack production configurations for a micro-UI web project. Specifically, the entry point and module federation identifiers for what was known as workbench are now labeled workbench-web. This renaming aims to refine how resources are managed and accessed, ensuring a clearer distinction and organization within the project's structure.

Changes

File Path	Change Summary
.../core/webpack.prod.js	Renamed entry point from workbench to workbench-web.
.../workbench/webpack.prod.js	Updated publicPath from "/workbench/" to "workbench-web" and name from "workbench" to "workbench-web".

🐰✨

In the land of code and web,
A change was made, a new thread to thread.
'Twas workbench once, now workbench-web instead,
A rabbit hops, with joy it treads.

Through files and lines, the changes spread,
A tale of updates, swiftly led.
🌟🐾

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 85147d3 and 7da85dc.

Files selected for processing (2)

• micro-ui/web/packages/core/webpack.prod.js (1 hunks)
• micro-ui/web/packages/workbench/webpack.prod.js (1 hunks)

Additional comments: 3

micro-ui/web/packages/workbench/webpack.prod.js (2)

• 10-10: The publicPath has been updated from "/workbench/" to "workbench-web". Ensure this change aligns with the deployment directory structure and asset referencing throughout the application. This adjustment is crucial for the correct location of deployed assets at runtime.
• 15-15: The name property in the ModuleFederationPlugin configuration has been changed from "workbench" to "workbench-web". This change is essential for consistent module identification across the application. Verify that this new name does not conflict with existing modules or naming conventions within the micro-UI architecture.

micro-ui/web/packages/core/webpack.prod.js (1)

• 24-24: The entry point for the workbench module has been renamed to workbench-web. This change is crucial for avoiding naming conflicts and ensuring correct module federation. Verify that all references to the workbench module throughout the application have been updated to reflect this new name.