You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
My project is angular15, using two-party library for angular13, because using npm i --legacy-peer-deps installation, so in node_modules two-party library shared the parent project angular15 dependencies, The setDisabledState method in the two-party library was accidentally called when the project was running, causing an internal error in my two-party library that the image could not be served due to network problems. After I changed the name of the setDisabledState method in the two-party library code, the program returned to normal. I suspect that there is a problem with angular's code isolation. Is it because my two-party library is referencing a dependency in @angular/core that calls an external setDisabledState method? Because I see a lot of setDisabledState calls in angular15.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
My project is angular15, using two-party library for angular13, because using npm i --legacy-peer-deps installation, so in node_modules two-party library shared the parent project angular15 dependencies, The setDisabledState method in the two-party library was accidentally called when the project was running, causing an internal error in my two-party library that the image could not be served due to network problems. After I changed the name of the setDisabledState method in the two-party library code, the program returned to normal. I suspect that there is a problem with angular's code isolation. Is it because my two-party library is referencing a dependency in @angular/core that calls an external setDisabledState method? Because I see a lot of setDisabledState calls in angular15.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
3
The text was updated successfully, but these errors were encountered: