Hello:
We are using a domain name for the adobe author instance (i.e. dom1), and we have another domain for the publish instance and angular application (call dom2).
We're using the lazymapto function, to load our components in runtime, just when it needed. The domain dom2, publish and angular application, works fine.
But the author instance in the editor mode, when it try to get the chunks for the application, raise an 404 error from the navigator, because the chunks files dont exists in the author instance (dom1), the chunks files exists in dom2. So the components don't are visibles in the editor mode.
We would like a new version for lazyMapTo function that considers a new URL parameter. This parameter will indicate the origin from AEM must to load the chunk component. This solution will help too for manage multiple environments (i.e dev,stage,prod)
We have used the urlDeploy parameter for the build instruction in package.json.
Hello:
We are using a domain name for the adobe author instance (i.e. dom1), and we have another domain for the publish instance and angular application (call dom2).
We're using the lazymapto function, to load our components in runtime, just when it needed. The domain dom2, publish and angular application, works fine.
But the author instance in the editor mode, when it try to get the chunks for the application, raise an 404 error from the navigator, because the chunks files dont exists in the author instance (dom1), the chunks files exists in dom2. So the components don't are visibles in the editor mode.
We would like a new version for lazyMapTo function that considers a new URL parameter. This parameter will indicate the origin from AEM must to load the chunk component. This solution will help too for manage multiple environments (i.e dev,stage,prod)
We have used the urlDeploy parameter for the build instruction in package.json.