Mike

Unfortunately, removing `Transformer` isn't solving our problem. What we are trying to do is to export the specific area of the stage to image. ```js // this is what pixi...

Sorry my bad, the workaround above has side effects and cannot be used in production, I'm just trying to declare the position issue from the editor.

@jamonholmgren Thanks for the reply, I got your point, I've found the type declaration below we can define our own data type on success and failure ```ts export type ApiResponse...

We also encounter this issue, the solution @jsimomaa given does fix the bug.

I believe the warning is from this line, https://github.com/pixijs/pixi-react/blob/ab3a672af3f589b4e2cdb24024e534b8145d7942/packages/react/src/stage/index.js#L272C1-L272C77 maybe we can ignore this because it has `provide support for Pixi v6 still` on the top of this function

Thanks a lot for the work, we look forward to this update.

Take a quick look into the source code, I think the problem is here ```diff once(e, fn) { const method = (value, prev, prop) => { fn(value, prev, prop); this.off(method);...

We are also facing this issue, and unfortunately AlphaFilter results in poor performance. Is there any other solution? Btw, our case is the shape overlaps itself.

Also facing this problem, the website on iOS keeps reloading and leads to "A problem repeatedly occurred". Is there any proper way to handle context lost using pixi@v8?