module imports with standalone components (assuming ivy)

[amitport]

🚀 feature request

Relevant Package

Angular core

Description

I want to load simple components dynamically (not necessarily async),
in its template it may use simple things like ngFor and I want to avoid the complexity of an additional NgModules

Describe the solution you'd like

I want to be able to declare a component:

@Component({
  template: '<div *ngFor="let i of list">{{i}}</div>',
})
class MyDynamicComponent {}

and just load it in another module that already imports CommonModule:

<ng-container *ngComponentOutlet=MyDynamicComponent "></ng-container>

Describe alternatives you've considered

currently I need to define an ngModule just for the import:

@Component({
  template: '<div *ngFor="let i of list">{{i}}</div>',
})
class MyDynamicComponent {}

@NgModule({
  declarations: [
    MyDynamicComponent 
  ],
  imports: [
    CommonModule
  ],
})
export class UselessAngularModule { }

it would also be better if I could add the import on the component itself:

@Component({
  template: '<div *ngFor="let i of list">{{i}}</div>',
  imports: [CommonModule]
})
class MyDynamicComponent {}

[amitport]

Hi, it's been a while, is this being considered?

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[amitport]

votes??

Two and an half years after a feature request is posted. A feature request that tries to resurface an issue with Angular that was posted as part of different bugs and features since day 1. ( This was not an issue with angular.js).

Unfortunately, or luckily, everyone who needed this feature probably already moved to react and others so I guess getting votes on this now is unlikely.

Your previous policy of just closing FR you didn't wish to do was better at least be direct about it and not wait for more than a couple of years to say that.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[JoostK]

Your previous policy of just closing FR you didn't wish to do was better at least be direct about it and not wait for more than a couple of years to say that.

Heya @amitport, sorry to hear you're upset about the recent introduction of voting (and having to wait 2.5 years without a reply, which is probably your larger complaint). The votes are just there to help measure interest in feature requests; requests will not be automatically closed or anything if there have been insufficient votes.

On the topic of this request, then. We're currently exploring what it would look like for components to be self-contained, in a project named "optional NgModules". The outcome of that project should be to allow what you're suggesting in this request.

[JoostK]

The description of #39695 also has a nice overview of the problem space, linking it here for visibility.

[npalladium]

@JoostK , is the source code of "optional NgModules" project mentioned above public? The closest I could find was this. Could you please link to it if possible? Thanks!

[JoostK]

@JoostK , is the source code of "optional NgModules" project mentioned above public? The closest I could find was this. Could you please link to it if possible? Thanks!

Expect an RFC out for this project soon!

[npalladium]

Oh! That's great!

Thanks for the lightning fast response @JoostK!

[pkozlowski-opensource]

For anyone tracking this issue - check our suggested solution described in the RFC: Standalone components, directives and pipes - making Angular's NgModules optional

[pkozlowski-opensource]

We are implementing standalone components, directives and pipes!

[angular-automatic-lock-bot]

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.}