TemporaryDisplayObject is not a constructor
See original GitHub issueUpdating to from 5.2.4
to 5.3
cause this issue:
Uncaught TypeError: _pixi_display__WEBPACK_IMPORTED_MODULE_2__.TemporaryDisplayObject is not a constructor
at new InteractionManager (interaction.es.js:946)
at Renderer.initPlugins (core.es.js:11310)
at new Renderer (core.es.js:11640)
at Function.create (core.es.js:11691)
at autoDetectRenderer (core.es.js:11926)
at new Application (app.es.js:70)
at new Game (game.js:29)
at index.js:7
at commitHookEffectListMount (react-dom.development.js:19765)
at commitPassiveHookEffects (react-dom.development.js:19803)
Webpack:
WARNING in ./node_modules/@pixi/interaction/lib/interaction.es.js 946:39-61
"export 'TemporaryDisplayObject' was not found in '@pixi/display'
pixi.js
version: 5.3
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Javascript "Not a Constructor" Exception while creating objects
The code as posted in the question cannot generate that error, because Project is not a user-defined function / valid constructor. function x(a,b,c){}...
Read more >TemporaryDisplayObject - PixiJS
private class TemporaryDisplayObject extends PIXI.DisplayObject. Constructor ... It does not have a capture phase, unlike most of the other events.
Read more >Model | Pixi3D - v2.1.0
Defined in node_modules/@pixi/display/index.d.ts:653. If the object has been destroyed via destroy(). If true, it should not be used.
Read more >playground/pixi.js.d.ts at master · englercj/playground - GitHub
A fun and simple way to create and share PixiJS demos. - playground/pixi.js.d.ts at master · englercj/playground.
Read more >PixiJS API Documentation
Natural Bounds | The bounds of an object in its own local space (not parent's space, ... private tempDisplayObjectParent: TemporaryDisplayObject; ...
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 FreeTop 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
Top GitHub Comments
Yeah, I believe that pixi-sound should use peerDependencies instead of direct dependencies. Would eliminate this issue and makes more sense.
@bigtimebuddy Maybe, I just removed pixi-sound and errors gone. I found as you mentioned there are two versions of pixi.js that the older version installed by pixi-sound. (In addition, I do not try to remove my package-lock.json before trying to remove pixi-sound, So I’m not sure that the reason for this issue is my package-lock file or pixi-sound)