npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@codebystella/flame-text

v0.1.1

Published

Embeddable oil-on-fire text effect with transparent canvas overlay

Readme

FlameText

Embeddable oil-on-fire text: transparent canvas overlay, glyph-aware emission (OpenType when a font URL is available, otherwise canvas raster), particle plume, temperature and intensity controls, optional ignition intro.

Repository: github.com/CodeByStella/flame-text
Live site (how to embed + interactive showcase): codebystella.github.io/flame-text/

Install (npm / bundler)

npm install @codebystella/flame-text
import { mount } from '@codebystella/flame-text'

Publishing is automated: create a GitHub Release whose tag matches package.json (e.g. tag v0.1.0 and version 0.1.0). You can also run Publish npm manually under Actions. Add an NPM_TOKEN repository secret (npm granular access token with Publish). Until the first successful publish, use the GitHub Pages script URLs below or install from git.

CDN / script embed

After each push to main, GitHub Actions builds the library, assembles a small site (landing + showcase), and publishes _site/ to GitHub Pages.

| What | URL (this repo) | | --------------------- | -------------------------------------------------------------------------------- | | Landing + demo | codebystella.github.io/flame-text/ | | IIFE (script tag) | https://codebystella.github.io/flame-text/flame-text.iife.js | | ESM | https://codebystella.github.io/flame-text/flame-text.js |

For other forks, replace owner/repo: https://OWNER.github.io/REPO/flame-text.iife.js.

jsDelivr / unpkg (after the package is on npm):

https://cdn.jsdelivr.net/npm/@codebystella/flame-text@VERSION/dist/flame-text.iife.js — pin VERSION (e.g. 0.1.0) or use @latest.

unpkg serves the same paths under https://unpkg.com/@codebystella/flame-text@VERSION/dist/….

Enable Pages once: repo Settings → Pages → Source: GitHub Actions.

If the deploy job fails with 404 (“Failed to create deployment”): Pages is not active for this repo yet, or Actions cannot use it. Fix: open Settings → Pages, set Source to GitHub Actions, save, wait a minute, then re-run the workflow. You need admin on the repo. For an organization repo, an org owner may need to allow GitHub Pages under org Settings → Pages (or Member privileges). Under Settings → Actions → General, ensure Workflow permissions is not locked to read-only in a way that blocks the workflow’s pages: write / id-token: write scopes.

Quick embed (ESM, npm)

<script type="module">
  import { mount } from '@codebystella/flame-text'
  mount('#hero', { temperature: 0.65, intensity: 1 })
</script>

Quick embed (ESM, URL)

<script type="module">
  import { mount } from 'https://codebystella.github.io/flame-text/flame-text.js'
  mount('#hero', { temperature: 0.65, intensity: 1 })
</script>

Quick embed (IIFE, CDN)

<script src="https://codebystella.github.io/flame-text/flame-text.iife.js"></script>
<script>
  window.addEventListener('DOMContentLoaded', function () {
    FlameText.mount('#hero', { fontUrl: '/fonts/MyFont.woff2', temperature: 0.7 })
  })
</script>

The host element must be in the DOM and should use normal flow (the library wraps it in a position: relative container and adds a pointer-events: none canvas on top). No opaque background is drawn; only flame pixels are composited.

API (short)

| Export | Description | | -------------------------------------- | ------------------------------------------------------------------ | | mount(selector \| element, options?) | Attach effect; returns { destroy, setTemperature, setIntensity } | | autoInit() | Mount every [data-flame-text] element with default options |

Options include flamePadding (extra canvas above/side/below the text so plumes are not clipped), fontUrl, temperature (0–1), intensity, particleCount, wind, ignition, respectReducedMotion. See docs/api.md.

Development

npm install
npm run dev      # demo at http://localhost:5173
npm run build    # dist/*.js + declarations
npm test
npm run lint

Preview the GitHub Pages bundle locally (same as CI):

npm run pages:preview   # build + assemble _site/ + static server

Docs

License

MIT