You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that pixi.js imports the display.js module but pixi-spine imports display.mjs. My problem is that mixins (from @pixi/events or @pixi/interaction) does not apply to the spine display objects. I think it's related to latest pixi version and this PR pixijs/pixijs#8505
@ivanpopelyshev it's a good question :)
I guess adding exports to package.json (for all pixi-spine packages) should help at least it did a trick for me. Honestly, I am also not a big modules expert @bigtimebuddy maybe you can give some advice here. Thanks!
Also, I can create PR if it's needed.
I did some research and I think the solution with adding exports to package.json for all pixi-spine packages is a good solution and it's the same as pixi.js has. Also, as another solution setting resolve.mainFields as ['main'] for webpack config resolve this issue. @ivanpopelyshev do you want me to create PR?
The issue is that pixi.js imports the
display.js
module but pixi-spine importsdisplay.mjs
. My problem is that mixins (from @pixi/events or @pixi/interaction) does not apply to the spine display objects. I think it's related to latest pixi version and this PR pixijs/pixijs#8505Pixi.js:
v6.5.1
pixi-spine:
v3.0.16
typescript:
v4.7.4
tsconfig info:
"module": "commonjs",
"moduleResolution": "node"
The text was updated successfully, but these errors were encountered: