resolveRemoteChunk url is not working on my side
See original GitHub issueChunkManager.configure({
resolveRemoteChunk: async (chunkId) => {
return {
url: http://localhost:5000/${chunkId}
,
};
},
});
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to fix webpack resolve-url-loader not working?
Received type object I read the doc for resolve-url-loader but I don't understand it. 2. Putting min-output.css in the root of the output...
Read more >The repack from callstack - GithubHelp
a webpack-based toolkit to build your react native application with full support of ... resolveRemoteChunk url is not working on my side.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m going to close this issue for now. If there are any more problems, feel free to reopen it.
Ok, in development mode all chunks are resolved and downloaded from the Development server. So
resolveRemoteChunk
is not called by design. By default theresolveRemoteChunk
is only used in production mode.Today I released a new version that allows to force the resolution to happen through
resolveRemoteChunk
.Please read the updated documentation:
In order to use Code Splitting from Webpack & Re.Pack in React Native, Re.Pack provides a native module. It should be automatically linked, but it’s good to do
pod install
for iOS to make sure it’s picked up.