Alex Prokop

Stopping after texture change is actually the functionality straight from PIXI: https://github.com/pixijs/pixijs/blob/dev/packages/sprite-animated/src/AnimatedSprite.ts#L389 I'm wary of making changes which diverge from how PIXI itself works, but this poses a challenge as...

This should be fixed now in `v7.0.0-alpha.0`, please install from `@pixi/react-pixi`

If you are working with a component that accepts render props then you could well need to use `useCallback` and return JSX from it. eg. if your render callback relies...

@ljharb > better would be to define a component at module level, and take the baz as a prop to that. Would you mind giving an example? Part of the...

> However, since the useMemo argument is just a render prop, not a component, this plugin shouldn't be checking RenderPropParams at all. In the `useMemo` case, there's no eslint error,...

Released in `v7.0.1`

@maximtwo @RJWadley - I believe you're both right (sort of). @maximtwo what you're describing is exactly how React works in user-land: A render will always happen on *any* prop change,...

Hey @mathedu4all you could do a couple of things here. 1) Don't use `Stage` but use the custom render method into a `Container` of your own custom Application: https://pixijs.io/pixi-react/render/#custom-render-call 2)...

Just adding `selectedItems.length` to the `useEffect` deps should fix this no? I've implemented done this in a useEffect in the consumer to fix this bug.