-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Cannot use with Angular 16 #457
Comments
This was referenced May 12, 2023
Closed
Give the new version a try: |
@hypery2k
|
@hypery2k would you please consider releasing current version as a stable release? |
great to here. Will make a v4 release Thanks for the feedback |
v4 is out out |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Current Behavior
Getting the following error when importing VisModule inside another module or standalone component after update to Angular 16.
Component imports must be standalone components, directives, pipes, or must be NgModules.
Expected Behavior
VisModule can correctly be imported when using angular 16.
Failure Information
Component imports must be standalone components, directives, pipes, or must be NgModules.
Steps to Reproduce
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
The text was updated successfully, but these errors were encountered: