mralbobo Posted April 10, 2020 Share Posted April 10, 2020 Hey, so I'm seeing some particularly strange loading behavior of pixijs-legacy after updating to angular 9 (using angular-cli as the build tool). In angular 8, everything was fine, but in 9 when trying to load pixijs-legacy it appears to just... completely ignore the legacy patch and ends up running the normal pixijs. Nothing cavas related is available and if you step through the execution, the auto-detect render code seems to be the non-legacy version. Imports follow the usual syntax import { Rectangle } from "pixi.js-legacy"; Now... the best part, everything works as expected in a minimal reproduction (angular seed project + pixi import), which makes it hard to report/ debug. So... mainly I'm just looking for some guidance into how pixi.js-legacy applies the legacy patch in the aid of better debugging. So that I can either work around it, or come up with an actual minimal repro. Quote Link to comment Share on other sites More sharing options...
ivan.popelyshev Posted April 10, 2020 Share Posted April 10, 2020 (edited) Double-pixi bug. Somehow you've got two versions of pixijs referenced, it happens, I dont know why, other people in pixijs team know how , ask them in github issues The usual recipe - "rm -rf node_modules" "rm package.lock" "npm i" Edited April 10, 2020 by ivan.popelyshev Quote Link to comment Share on other sites More sharing options...
mralbobo Posted April 10, 2020 Author Share Posted April 10, 2020 (edited) I'm going to be sad if it's just the standard npm cache problem lol. ...yep, that did it. As promised ? Thanks! Edited April 10, 2020 by mralbobo ivan.popelyshev 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.