Skip to content
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

After upgrading to v17 unable to see imported components #55000

Closed
Synectron opened this issue Mar 22, 2024 · 3 comments
Closed

After upgrading to v17 unable to see imported components #55000

Synectron opened this issue Mar 22, 2024 · 3 comments
Labels
area: core Issues related to the framework runtime needs reproduction This issue needs a reproduction in order for the team to investigate further
Milestone

Comments

@Synectron
Copy link

Which @angular/* package(s) are the source of the bug?

upgrade

Is this a regression?

Yes

Description

I upgraded my project to v17 but now all the imported components are not loading. I even did standalone false to all components, and also tried doing standalone true and imported all necessary components but to no avail. This was working in v16.

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)

Angular CLI: 17.3.0
Node: 18.15.0
Package Manager: npm 9.6.7
OS: win32 x64

Angular:17.3.0
... animations, cli, common, compiler, compiler-cli, core, form
... language-service, localize, platform-browser
... platform-browser-dynamic, router, service-worker

Package                     Version
------------------------------------------------------
@angular-devkit/architect    0.1703.0 
@angular-devkit/core         17.3.0 
@angular-devkit/schematics   17.3.0  
@schematics/angular          17.3.0 
@angular-devkit/build-angular17.3.0
ng-packagr                   17.3.0
rxjs                         7.8.1
typescript                   5.4.2
zone.js                      0.14.4

Anything else?

No response

@JoostK
Copy link
Member

JoostK commented Mar 22, 2024

Without a runnable reproduction this won't be actionable, unfortunately.

@JoostK JoostK added the needs reproduction This issue needs a reproduction in order for the team to investigate further label Mar 22, 2024
@dylhunn dylhunn added the area: core Issues related to the framework runtime label Mar 27, 2024
@ngbot ngbot bot added this to the Backlog milestone Mar 27, 2024
@JeanMeche
Copy link
Member

Hi, without feedback from you we'll close this issue.
If you have a reproduction of this issue, feel free to open a new issue.

@JeanMeche JeanMeche closed this as not planned Won't fix, can't repro, duplicate, stale Apr 3, 2024
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: core Issues related to the framework runtime needs reproduction This issue needs a reproduction in order for the team to investigate further
Projects
None yet
Development

No branches or pull requests

4 participants