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
The paths in remoteHostEntry.js should correctly reference the chunks from the chunks directory, not from assets/chunks.
What is actually happening?
After upgrading to @originjs/vite-plugin-federation version 1.3.7, the paths in remoteHostEntry.js are incorrectly pointing to assets/chunks instead of the correct chunks directory. This issue is due to the update that makes the remote entry chunk use the base path from the Vite config.
original path of the file : dist > chunks > chnk-__federation_expose_Services.js
Path inside remoteEntry.js : "
./services":()=>{
return __federation_import('./assets/../chunks/chnk-__federation_expose_Services.js').then(module =>Object.keys(module).every(item => exportSet.has(item)) ? () => module.default : () => module)},
The text was updated successfully, but these errors were encountered:
Versions
Reproduction
What is Expected?
The paths in remoteHostEntry.js should correctly reference the chunks from the chunks directory, not from assets/chunks.
What is actually happening?
After upgrading to @originjs/vite-plugin-federation version 1.3.7, the paths in remoteHostEntry.js are incorrectly pointing to assets/chunks instead of the correct chunks directory. This issue is due to the update that makes the remote entry chunk use the base path from the Vite config.
The text was updated successfully, but these errors were encountered: