tsParticles Trail Effect

tsParticles additional trail effect.

Quick checklist

1. Install @tsparticles/engine (or use the CDN bundle below)
2. Call the package loader function(s) before tsParticles.load(...)
3. Apply the package options in your tsParticles.load(...) config

How to use it

CDN / Vanilla JS / jQuery

The CDN/Vanilla version JS has one required file in vanilla configuration:

Including the tsparticles.effect.trail.min.js file will export the function to load the effect:

loadTrailEffect
Copy

Usage

Once the scripts are loaded you can set up tsParticles and the effect like this:

(async () => {
  await loadTrailEffect(tsParticles);

  await tsParticles.load({
    id: "tsparticles",
    options: {
      /* options */
      /* here you can use particles.effect.type: "trail" */
    },
  });
})();
Copy

ESM / CommonJS

This package is compatible also with ES or CommonJS modules, firstly this needs to be installed, like this:

$ npm install @tsparticles/effect-trail
Copy

or

$ yarn add @tsparticles/effect-trail
Copy

Then you need to import it in the app, like this:

const { tsParticles } = require("@tsparticles/engine");
const { loadTrailEffect } = require("@tsparticles/effect-trail");

(async () => {
  await loadTrailEffect(tsParticles);
})();
Copy

or

import { tsParticles } from "@tsparticles/engine";
import { loadTrailEffect } from "@tsparticles/effect-trail";

(async () => {
  await loadTrailEffect(tsParticles);
})();
Copy

Option mapping

• Effects are usually enabled through dedicated package loaders and effect-specific options.
• Package scope: trail
• Start from the usage snippet in this README, then merge with your main options object incrementally.

Common pitfalls

• Calling tsParticles.load(...) before loadTrailEffect(...)
• Verify required peer packages before enabling advanced options
• Change one option group at a time to isolate regressions quickly

Related docs

• All packages catalog: https://github.com/tsparticles/tsparticles
• Main docs: https://particles.js.org/docs/