Skip to content

Conversation

@greatertomi
Copy link
Contributor

@greatertomi greatertomi commented Nov 17, 2025

Checklist

  • JIRA - LW-13671
  • Proper tests implemented
  • Screenshots added.

Proposed solution

This creates an LMP build from Lace

Testing

Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met

Screenshots

Screen.Recording.2025-11-18.at.00.mp4

@greatertomi greatertomi requested review from a team as code owners November 17, 2025 23:37
@lace-bot
Copy link
Collaborator

lace-bot commented Nov 17, 2025

Allure Report

allure-report-publisher generated test report!

processReports: ✅ test report for 1833d829

passed failed skipped flaky total result
Total 32 0 5 0 37

@greatertomi greatertomi force-pushed the feat/lw-13671-v1-lmp-bundle branch from 06d68c4 to 2face67 Compare November 18, 2025 08:31

## Creating an LMP Bundle Build
To create an LMP bundle for Lace:
- Place the LMP build at the repository root in `./lmp-build`
Copy link
Member

Choose a reason for hiding this comment

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

We should have scripts that do it. It can be achieved by adding lace-platform as git submodule/subrepo.

Suggested change
- Place the LMP build at the repository root in `./lmp-build`

Copy link
Contributor Author

@greatertomi greatertomi Nov 18, 2025

Choose a reason for hiding this comment

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

I started by adding lace-platform as a submodule/subrepo, but ran into several build issues. @pczeglik-iohk recommended we do a manual copy of the build from lace-platform for now, and that way we don't reveal any code from lace-platform since it is unreleased

Copy link
Member

Choose a reason for hiding this comment

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

Can we do a manual git clone or symlink and have it gitignored?

Copy link
Member

Choose a reason for hiding this comment

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

Can we manually copy entire lace-platform instead and move the build script to lace/apps/lmp-bundle?

Copy link
Contributor Author

@greatertomi greatertomi Nov 19, 2025

Choose a reason for hiding this comment

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

I tried the symlink approach, and I am having the same issue I have with submodules. I have to install some of lace-platform dependencies. Then there's a conflict with the typescript version.

Copy link
Member

Choose a reason for hiding this comment

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

Please hoist all new files and npm scripts into a new app directory so that the changes are better isolated/encapsulated: apps/lmp-bundle

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Reorganized on b8fda2e

@greatertomi greatertomi force-pushed the feat/lw-13671-v1-lmp-bundle branch from 2face67 to a0dc5fc Compare November 18, 2025 13:32

## Creating an LMP Bundle Build
To create an LMP bundle for Lace:
- Place the LMP build at the repository root in `./lmp-build`
Copy link
Member

Choose a reason for hiding this comment

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

This is root readme, the path seems to be wrong. Please self-review and make sure it's cohesive.

Suggested change
- Place the LMP build at the repository root in `./lmp-build`
- Place the LMP build at the repository root in `./apps/lmp-bundle/lmp-build`

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This README.md is within the apps/lmp-bundle directory. Do we need to specify the path from the root?


## Creating an LMP Bundle Build
To create an LMP bundle for Lace:
- Place the LMP build at the repository root in `./lmp-build`
Copy link
Member

Choose a reason for hiding this comment

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

Can we do a manual git clone or symlink and have it gitignored?

To create an LMP bundle for Lace:
- Place the LMP build at the repository root in `./lmp-build`
- From the repository root run `yarn build:bundle:full`
- The command will produce a `.dist` file in the repository root.
Copy link
Member

Choose a reason for hiding this comment

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

Please make sure it's contained in the new app

Suggested change
- The command will produce a `.dist` file in the repository root.
- The command will produce a `apps/lmp-bundle/.dist` file in the repository root.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same as this

"watch:sw": "run -T webpack --config webpack.sw.dev.js --progress --watch",
"watch:project": "run-p watch:sw watch:app"
"watch:project": "run-p watch:sw watch:app",
"build:bundle:prepare": "yarn cleanup:dist && WEBPACK_PUBLIC_PATH=/sw/ yarn build:sw && WEBPACK_PUBLIC_PATH=/app/ yarn build:app && WEBPACK_PUBLIC_PATH=/app/ yarn build:cs"
Copy link
Member

Choose a reason for hiding this comment

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

Can we hoist this script to apps/lmp-bundle?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed on f172610

@sonarqubecloud
Copy link

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