-
-
Notifications
You must be signed in to change notification settings - Fork 927
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
Stage.d.ts make StageConfig container optional for use in node environment #1797
Comments
Interested in making a pull request? |
daniatic
pushed a commit
to daniatic/konva
that referenced
this issue
Jul 31, 2024
Thanks |
No, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The readme states that the container property in StageConfig can be omitted for use in a Node environment. However, the type definition still requires the container property, causing a conflict. I can simply ignore this conflict, but would it be possible to make the property optional?
The text was updated successfully, but these errors were encountered: