Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate frontend-platform build process #629

Open
arbrandes opened this issue Jan 23, 2023 · 2 comments
Open

Investigate frontend-platform build process #629

arbrandes opened this issue Jan 23, 2023 · 2 comments
Assignees

Comments

@arbrandes
Copy link
Contributor

The way frontend-platform is built makes it impossible to npm-install directly from git. Investigate why this is the case and report back in the forum thread.

@arbrandes arbrandes self-assigned this Jan 23, 2023
@davidjoy
Copy link

davidjoy commented May 1, 2023

I'd be happy to help provide context/clarity on the frontend-platform build process - it looks like the forum thread author found a solution to their localization issues, if I read the thread right? But also that folks may be confused how the libraries are packaged for npm, how they work with module.config.js, etc.

@arbrandes
Copy link
Contributor Author

I met Dimitris at the conference, and he brought the localization issue up. He managed a workaround, but the true fix is going to come out not of the npm-installability issue, but of us revamping how i18n is done for MFEs. I.e., out of scope here.

As for the issue described here, me and Pedro are working on how to port frontend-platform over to MFE Domains Land, and a possibly suitable alternative might come out of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants