[WIP] Build process for frontendbase apps - #282
Closed
holaontiveros wants to merge 7 commits into
Closed
Conversation
This was referenced Mar 11, 2026
Collaborator
|
Closing in favor of #284. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Basic details
This is the first step for the build process of the frontend apps and to allow
Assumptions
This only uses a single build for template-site, the other MFES with a frontendbase branch are not directly pulled during the build, so you need to be sure your packages.json for the template-site has everything to be able to be build.
If the packages that are intented to be used (the apps to be used in the apps array) are not published (so no dist folder yet) you can point to a git branch and they need to have a package.json prepare script and include the right files for it to be build as part of the npm install.
This way you'll endup with the package installed, transpiled and ready to be used, and this magic will only happen when the package is installed from a git repo, which means the build / install dev and normal dependencies will only happen when you need to use a non-published package.
Also for now, the aggregator repo needs to have the same public path as the app_name for the app in this case and for now that's template-site which means
PUBLIC_PATH=/template-site/because that will allow all the assets to be served properly.How to add a frontendapp
In order to mark something as a frontendbase app you need a plugin that looks like:
Any app that it's on this list will be considered a fronend-app so when Caddy shows the content for it, it will show the one on template-site instead of the normal app.