-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(angular): use esm2022 for secondary entrypoints in ng-packagr-lite executor #20130
fix(angular): use esm2022 for secondary entrypoints in ng-packagr-lite executor #20130
Conversation
…in ng-package-lite
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 8886a7c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
still can't build my angular project with incremental esbuild and a library with secondary entrypoints... I guess this is the fix for that, as this is supposed to be fixed in ng-packagr now... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
This is a good catch. I left a comment with a suggested change. We need to account for the differences between the supported Angular versions.
...ors/ng-packagr-lite/ng-packagr-adjustments/ng-package/entry-point/write-package.transform.ts
Outdated
Show resolved
Hide resolved
…secondary-entrypoints
…e executor (#20130) Co-authored-by: Leosvel Pérez Espinosa <[email protected]> (cherry picked from commit 96043fb)
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
Expected Behavior
Related Issue(s)
Fixes #