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

Upgrade to Angular 18 #186

Open
CharlieGreenman opened this issue May 28, 2024 · 2 comments
Open

Upgrade to Angular 18 #186

CharlieGreenman opened this issue May 28, 2024 · 2 comments

Comments

@CharlieGreenman
Copy link

I'm submitting a

Feature request

Current behavior

Currently on Angular 17

Expected behavior

Should be available for Angular 18 as well

Minimal reproduction of the problem with instructions

No response

What is the motivation / use case for changing the behavior?

No response

Environment

No response

@geromegrignon
Copy link
Collaborator

Hello PR are welcomed.

Should be available for Angular 18 as well

It's already available for Angular 18 as the current version peerDependencies are:

"peerDependencies": {
    "@angular/common": ">=16.0.0",
    "@angular/core": ">=16.0.0"
  },

@CharlieGreenman
Copy link
Author

I will try. Would be cool to use signals as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants