Secondary entrypoints updates not applied when using npm link
See original GitHub issueWhich @angular/* package(s) are the source of the bug?
compiler, core
Is this a regression?
No
Description
When using secondary entrypoints changes in linked library are not applied to application. When using primary entrypoints it works well. Please see attached repository.
Please provide a link to a minimal reproduction of the bug
https://github.com/Ledzz/ivy-secondary-entrypoints
Please provide the exception or error you saw
No error, the app reloads but changes are not applied.
Please provide the environment you discovered this bug in
Angular v12.2.0
NodeJS v14.16.1
Npm v6.14.12
Yarn v1.22.10
Windows 10
Anything else?
No response
//cc @Ledzz
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Secondary entry point not working consistently in typescript <2.6
I was facing this issue as well and figured that the problem is likely due to a missing index.d.ts file in the secondary...
Read more >Package that is linked with npm link doesn't update
Had similar problem with linked package - npm link dep was picking up old version of "dep". Running npm link (again) in "dep"...
Read more >Creating Secondary Entry Points for your Angular Library
In this article, we will take a look at how we can utilise ng-packagr secondary entry points to split our Angular Library even...
Read more >Building an Angular Library with multiple entry points | Articles
A npm package can have additional entry points, called secondary entry points (or subentry points). An example is Angular Material which has ...
Read more >Angular Libraries Adding Secondary EntryPoints - YouTube
This is the second part of Angular Libraries, where we add a secondary entrypoint to make Angular libraries Tree-shakable.
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
@SpeedHighway @Kickassbadboy There are three alternative solutions outlined in an SO answer.
As a workaround you can run the build without cache