Ensure CJS-only build for Lambda@Edge and return null instead of error before target-app-versions.json creation #121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes the following changes:
1. Modify build output to generate only CJS
• Lambda@Edge supports only CommonJS (CJS), so the build process is adjusted to produce only CJS output.
2. Return null instead of throwing an error when target-app-versions.json is not yet created
• Previously, an error was thrown if target-app-versions.json was missing.
• Now, it returns null to prevent unnecessary failures.
These changes improve compatibility with Lambda@Edge and enhance error handling. 🚀