Rollup 1.26 breaks fesm5 build of libraries
See original GitHub issueType of Issue
[x ] Bug Report
[ ] Feature Request
Description
ng-packagr
declares a dependency on rollup
that includes version 1.26.0
. With this version we see that the fesm5
build of our library contains * exports.
I think that this is related to https://github.com/rollup/rollup/issues/3196
This basically breaks the build of all of our libraries.
I suggest to set the dependency of ng-packagr
to rollup@~1.25
until rollup fixes the bug.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Rollup config error on dynamic import during library build #1285
This bug relates to building angular library which uses dynamic imports. Consider building foo library with the command ng build foo . When...
Read more >Code-splitting for libraries—bundling for npm with Rollup 1.0
Our library project. For this example, we will be building a collection of awesome utilities to convert strings to upper and lower case...
Read more >How to get rollup to deal with node based libraries in the ...
You should first solve problems in your terminal. Which are like compile errors. Then ones in a browser, which are more like runtime....
Read more >TypeScript library tips: Rollup your types! | by Martin Hochel
breaks encapsulation, because consumers can use/access parts of our codebase, that are not part of public API surface (which will not work if ......
Read more >How to Bundle JavaScript With Rollup — Step-by-Step Tutorial
Rollup is a next-generation JavaScript module bundler. Author your app or library using ES2015 modules, then efficiently bundle them up into a single...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Indeed this issue is caused by https://github.com/rollup/rollup/issues/3196
Will lock rollup and cut a release tomorrow morning CET.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. This action has been performed automatically by a bot.