dranitski Posted October 15, 2019 Share Posted October 15, 2019 Steps to reproduce: git clone https://[email protected]/dmitrydranitski/pixijs-5.1.1-5.1.5-update-bug.git cd into dir npm i npm run dev go to the url (https://localhost:8080 by default) you should see the page Ctrl+C - stop the webpack-dev-server rm -rf node_modules npm i [email protected] npm run dev go to the url (https://localhost:8080 by default) The code is not working. I can not see the reason, seems like a bug? Thanks in advance for any help! Quote Link to comment Share on other sites More sharing options...
ivan.popelyshev Posted October 15, 2019 Share Posted October 15, 2019 Known bug. Two versions of pixi exist at the same time, renderers are registered in only one of them. "Remove package.lock and node_modules" helps. Quote Link to comment Share on other sites More sharing options...
dranitski Posted October 15, 2019 Author Share Posted October 15, 2019 https://github.com/pixijs/pixi.js/issues/6171#issuecomment-542156688"Remove package.lock and node_modules" helped. Thanks! ivan.popelyshev 1 Quote Link to comment Share on other sites More sharing options...
USER@$ Posted December 17, 2020 Share Posted December 17, 2020 I am facing same type of issue but removing package.lock and node_modules didn't work for me. In my typescript project pixi.js is used. We were using it through node_modules but now we tried to use pixi.js externally but it is not working. Steps to reproduce: Replace local path of pixi.js with cdn path in project's html file Added pixi.js in externals section of webpack.config.ts Expected behaviour: Application should run without any error Current behaviour: Getting following error. PIXI is undefined here 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.