-
Notifications
You must be signed in to change notification settings - Fork 23
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 Pixi.js v8 #123
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@hairyf Oh, I forgot, but, feel free to let me know what you think of this or if you have any thoughts regarding an upgrade! ❤️🫡 |
@nightgrey no problem, let's work together to complete this arduous task |
Hey @hairyf, sorry for not contributing further! I might take another stab at it in the future, but it's unlikely and I can't promise anything </3 Thank you for your library! |
Any update for this? |
Hello there 👋 , just ran into this PR while looking for activity Vue3-pixi's adoption of Pixi v8. Are the TODOs in the description still accurate as to what's left to getting it done? Or has something else been done elsewhere? If not, how could I help? I've not much expertise on Pixi, but I have experience with Vue |
As the title says, this starts the upgrade of
vue-pixi3
to v8 (fixes #74). Help from anyone is appreciated!Todo:
vue3-pixi/src/elements
vue3-pixi/src/renderer/default-renderer.ts
vue3-pixi/src/elements/props
patchProp
nodeOps
is correctLinks