You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we add two different applications with steal bundled and they are deployed on different pathname or different domains, the applications does not work as expected.
The second loaded applications tries to load for a stealConfig.js file and when the application loads static content it tries to load the content from the main HTML file baseURL.
The app should work without any failing resource request.
Actual results:
The second application tries to load stealConfig.js file.
Both applications fails to load when trying to load the static content assets like CSS files.
Environment:
Software
Version
Steal version
2.2.4
Steal-tools version
2.2.6
node -v
v12.13.0
npm -v
6.12.0
Browser
Chrome
Operating system
Linux
The text was updated successfully, but these errors were encountered:
In this case the apps source code are available on the same repo and below the same root folder, but what I'm trying to have is the apps be available from different domains/path names, developed by different teams and source code hosted on different repos, something similar to micro-frontends.
Something similar to what single-spa does, but in my case using web components, to join the different apps into a same html.
How often can you reproduce it?
Description:
When we add two different applications with steal bundled and they are deployed on different pathname or different domains, the applications does not work as expected.
The second loaded applications tries to load for a
stealConfig.js
file and when the application loads static content it tries to load the content from the main HTML file baseURL.Steps to reproduce:
Expected results:
The app should work without any failing resource request.
Actual results:
The second application tries to load
stealConfig.js
file.Both applications fails to load when trying to load the static content assets like CSS files.
Environment:
The text was updated successfully, but these errors were encountered: