We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For more information, see the CONTRIBUTING guide.
CONTRIBUTING
In Angular since v15.2 the standalone bootstrapping API is the default way. That means, there is not app.module.ts any more. Also the routing is now defined in a class that is called ApplicationConfig, see https://angular.io/guide/router#defining-a-basic-route.
app.module.ts
ApplicationConfig
We would like to stay with the default Angular pattern in the future, so It would be nice if piral-ng support this.
[Optionally, outline any pros and cons you can currently think of to provide the basis for a solid discussion]
The text was updated successfully, but these errors were encountered:
This is now available via piral-ng/standalone. A dedicated module for creating / converting modern Angular standalone components.
piral-ng/standalone
Sorry, something went wrong.
No branches or pull requests
New Feature Proposal
For more information, see the
CONTRIBUTING
guide.Description
In Angular since v15.2 the standalone bootstrapping API is the default way. That means, there is not
app.module.ts
any more. Also the routing is now defined in a class that is calledApplicationConfig
, see https://angular.io/guide/router#defining-a-basic-route.Background
We would like to stay with the default Angular pattern in the future, so It would be nice if piral-ng support this.
Discussion
[Optionally, outline any pros and cons you can currently think of to provide the basis for a solid discussion]
The text was updated successfully, but these errors were encountered: