Error when migrated to v5.0.5 with webpack setup
Describe the bug
When migrated to Repack v5.0.5 using the migration guidelines and webpack setup , getting the following error:
[ScriptManager] Failed to load script: [ScriptDownloadFailure] {"cache": true, "caller": undefined, "locator": {"absolute": false, "body": undefined, "fetch": true, "headers": undefined, "method": "GET", "query": "platform=ios", "retry": undefined, "retryDelay": undefined, "timeout": 500000, "uniqueId": "mfe1", "url": "http://localhost:9005/mfe1.container.bundle", "verifyScriptSignature": "off"}, "scriptId": "mfe1"} {"originalError": [Error: Request should have returned with 200 HTTP status, but instead it received 404]}
System Info
Repack v5.0.5
webpack: 5.98.0
React Native: 0.74.6
Platform: IOS
Re.Pack Version
5.0.5
Reproduction
none
Steps to reproduce
yarn start yarn ios
when MFE is getting loaded getting the error
hey, can you please try 5.0.6? It's probably the ResolverPlugin issue that was solved in 5.0.6
Hi @jbroma , I'm migrating my project to RSPack and I plan on using mF2. Would retry logic work for the mini-apps if they fail to load due to network issues.
Hi @jbroma , I'm migrating my project to RSPack and I plan on using mF2. Would retry logic work for the mini-apps if they fail to load due to network issues.
yes, if you use retry logic from ScriptManager it will work - it will be easy to add in 5.1 with addition of ScriptManager hooks - check the 5.1 release for more details: https://github.com/callstack/repack/releases/tag/%40callstack%2Frepack%405.1.0-rc.0
Hi @jbroma , I'm migrating my project to RSPack and I plan on using mF2. Would retry logic work for the mini-apps if they fail to load due to network issues.
yes, if you use retry logic from ScriptManager it will work - it will be easy to add in 5.1 with addition of ScriptManager hooks - check the 5.1 release for more details: https://github.com/callstack/repack/releases/tag/%40callstack%2Frepack%405.1.0-rc.0
Wow wow wow. I can't wait to try this out. I'd drop my feed back here
This issue has been marked as stale because it has been inactive for 30 days. Please update this issue or it will be automatically closed in 14 days.
@liouskoothamattathilbaby did you manage to resolve this issue?
Closing since the issue has been stale for a very long time and the bug report is to vague to act upon - we can reopen the issue after providing a reproduction that can isolate (or narrow) this problem.
Hi @jbroma , please bear with me for the late reply, with the latest repack version 5.1.1, this issue is resolved and was able to successfully load MFE using rspack. Thanks for your continued support and hope this community will continue to grow and acts as an ecosystem for MFE architecture.
Hi @jbroma , please bear with me for the late reply, with the latest repack version 5.1.1, this issue is resolved and was able to successfully load MFE using rspack. Thanks for your continued support and hope this community will continue to grow and acts as an ecosystem for MFE architecture.
glad to hear that 🙌