Building add-on creates a remoteEntry that expects a module, but no module directory

[tmarnell]

When ADDON_NAME is set in the build settings, npm run build creates a distribution with no internal directory for the module. However, the generated remoteEntry.js first checks for the nonexistent directory and throws the error 'Module "'+s+'" does not exist in container,' and the add-on will not load in Primo NDE.

[tmarnell]

I found the issue: Primo NDE looks for the module based on the name in Alma, not the name in the files. So the ADDON_NAME and the name in Alma must match exactly, so that in webpack.config.js, the key in the ModuleFederationPlugin for "exposes" will be "./" followed by the Add-On Name in Alma. Adding these instructions to the README would be helpful.

[ShoulM]

I found the issue: Primo NDE looks for the module based on the name in Alma, not the name in the files. So the ADDON_NAME and the name in Alma must match exactly, so that in webpack.config.js, the key in the ModuleFederationPlugin for "exposes" will be "./" followed by the Add-On Name in Alma. Adding these instructions to the README would be helpful.

Thanks for your input. Feel free to open a PR for the documentation if you think this needs to be explained better.