Timo Kämäräinen

The tests in `pixi-particles` are already done with Electron so it might not even be a huge amount of work.

@ivanpopelyshev do you have a plan/estimate when you would be looking into this? I could take a peek at some point now that my [pixi-particles v6 port PR](https://github.com/pixijs/pixi-particles/pull/152) has been...

> The problem is that i want to separate it to multiple packages so it will be something like pixi-spine by structure. @ivanpopelyshev I guessed you might have some plans...

Easiest way to reproduce/fix these issues is to enable `strictNullChecks: true` in the project's `tsconfig.json`. That'll throw a bunch of compile errors. Though looking at the core Pixi.js repository it...

Okay seems like there is already an issue about this for Pixi itself: https://github.com/pixijs/pixijs/issues/8852

I cloned the repo to look into this but I ran into other weird issues. For example the base package has the peer dependencies defined like this: ``` "@pixi/constants": "^6.0.2",...

Not sure what's causing the problems I'm having but it seems some PIXI packages are version 6.0.4 and some 6.1.0 which causes all sorts of type incompatibilities when trying to...

I think ^ is more common. It allows for minor updates, ie. 6.x.x whereas ~ allows only patch releases, ie. 6.0.x - https://docs.npmjs.com/about-semantic-versioning However according to strict semantic versioning the...

`3.0.8` seems to work. At least it compiles without errors. Can't really test it further than that yet because there's a bunch of breaking changes in PIXI 6.1.0 that I...

We have only added the packages that we directly use as dependencies which previously were installed automatically so basically all the stuff that was moved to peer dependencies needs to...