repack
repack copied to clipboard
Feature: OutputPlugin's optional entryName
Description
In certain scenarios, there is a requirement to deploy a container separately from any associated app. This necessitates building with an empty object {}
for the entry configuration. This approach ensures that only the remote entry and related chunks are built. However, this causes Re.Pack's OutputPlugin to throw an exception.
To address this issue, the current workaround involves individually expanding the Re.Pack plugins instead of utilizing Repack.RepackPlugin. This workaround allows for manually passing the entryName to the OutputPlugin, thereby resolving the exception.
Expected behaviour
The OutputPlugin should handle an empty entry object without throwing an exception
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.
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.
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.
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.
Closed by #539