A portable PixiJS v8 particle workflow: author, validate, export, run

[Asami]

I’ve been working through a cleaner way to keep particle effects out of PixiJS scene code while still making them versionable and easy to review.

The workflow that has held up best for PixiJS v8 projects is:

1. Author each effect as plain JSON in a project folder.
2. Validate and export a self-contained out/vfx bundle with a manifest, effect JSON, and textures.
3. Load the bundle once, attach the renderer to the Pixi stage, and update it from the app ticker.
4. Destroy the runtime during scene teardown so emitters and textures do not leak.

The integration boundary can stay small:

import { PixiVfxRenderer } from "nixie-fx/pixi";

const runtime = new PixiVfxRenderer({
  parent: app.stage,
  textureProvider
});

app.ticker.add((ticker) => {
  runtime.update(ticker.deltaMS / 1000);
});

Keeping asset loading in the game and simulation in the effect runtime makes the exported effects deterministic, portable, and straightforward to keep in source control.

For anyone testing the same approach, the complete PixiJS v8 walkthrough is here:
https://nixiefx.com/pixijs-particle-effects/

Disclosure: I’m sharing documentation maintained by the NixieFX team.