Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
pixi.js-legacy not work
See original GitHub issueExpected Behavior
My website run on virtual machine that without gpu, so I use pixi.js-legacy to use canvas not webgl.
Current Behavior
Just new Application.
then:
Possible Solution
Steps to Reproduce
Environment
pixi.jsversion: “pixi.js-legacy”: “^5.2.0”,- Browser & Version: 66.0.3359.139
- OS & Version: window 7
- Running Example: url
and more infomations:
chrome://gpu:
chrome://flags:
Issue Analytics
- State:
- Created 4 years ago
- Comments:7
Top Results From Across the Web
pixi.js-legacy not work · Issue #6256
My website run on virtual machine that without gpu, so I use pixi.js-legacy to use canvas not webgl. Current Behavior. Just new Application....
Read more >pixi.js-legacy
Start using pixi.js-legacy in your project by running `npm i pixi.js-legacy`. There are 40 other projects in the npm registry using ...
Read more >pixi.js-legacy": "^5.3.0" problem
I update pixi.js-legacy from 5.2.1 to 5.3.0. After this there is error Cannot read property 'baseTexture' of null.
Read more >Create legacy fallback for pixi.js
js -legacy" for fallback canvas2d support. But how do I do so? Documentation says that one's supposed to import PIXI like that using...
Read more >PIXI.Application
Note: Setting this parameter to false does NOT stop the shared ticker even ... when using pixi.js-legacy or @pixi/canvas-renderer modules, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I bet its webpack issue again, did you update your pixi from 5.1? If so, remove node_modules, package.lock and
npm iit all again.Two PIXI versions (5.1 and 5.2) built into same bundle can trigger this warning too.
OK, This is my problem, I just delete package.lock.json but not delete yarn.lock. Sorry to take your time.