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

@heyphat/piner

v0.9.0

Published

Clean-room Pine Script v6 engine for the browser and Node

Readme

Piner

CI npm License: AGPL v3

A clean-room Pine Script v6 engine in TypeScript — compile and run Pine indicators and strategies anywhere, browser-first. Designed from the public TradingView v6 docs only.

Piner is the engine behind fractalchart.com, which is its primary use case, and it's published here as a standalone open-source library.

Fractal Chart, powered by Piner

compile(src) lexes → parses → analyzes → emits JS and an interpreter oracle; the two backends are cross-checked for byte-for-byte identical output. The full v6 language runs end-to-end, plus broad built-in, input, drawing, request.security, and strategy coverage. See docs/compiler-design.md.

Documentation

All docs live in docs/:

Install

npm install @heyphat/piner
# or: bun add @heyphat/piner / pnpm add @heyphat/piner / yarn add @heyphat/piner

Ships ESM + CJS builds and TypeScript types. Works in the browser and in Node ≥ 18.

Develop

Requires Bun ≥ 1.2.

bun install
bun test          # full suite incl. the two-backend (js vs interp) cross-check
bun run typecheck # tsc --noEmit
bun run build     # ESM + CJS (bun) + d.ts (tsc) into dist/

See CONTRIBUTING.md for the clean-room policy and the two-backend invariant before opening a PR.

What works today

Compile Pine v6 source and run it against a data feed:

import { compile, Engine, ArrayFeed } from '@heyphat/piner';

const compiled = compile(`//@version=6
indicator("SMA cross", overlay=true)
fast = ta.sma(close, 5)
slow = ta.sma(close, 20)
plot(fast, title="fast")
plot(slow, title="slow")
plotshape(ta.crossover(fast, slow), title="up")
`);

const engine = new Engine(compiled, new ArrayFeed(bars)); // backend: 'js' (default) | 'interp'
await engine.run({ symbol: 'BTCUSD', timeframe: '60' });
engine.outputs.plots.get(0); // → { id, title, data: number[] }

// realtime: each tick re-runs the open bar (repaint), commit on close
engine.tick(liveBar, /* isClose */ false);

compiled.interpret is the AST-interpreter backend over the same runtime — used as the correctness oracle (cross-checked against the generated JS). The runtime can also execute a hand-written ScriptFn directly (see test/runtime-core.test.ts).

Library import / export

Pine import Publisher/Lib/Version [as alias] resolves from an in-memory registry you pass to compile — no network, no filesystem, fully deterministic:

import { compile, Engine, ArrayFeed } from '@heyphat/piner';

const compiled = compile(
  `//@version=6
indicator("uses a library")
import alice/mathlib/1 as ml
plot(ml.zscore(close, 20), title="z")
`,
  {
    libraries: [
      {
        key: 'alice/mathlib/1',
        source: `//@version=6
library("MathLib")
export zscore(float src, int len) => (src - ta.sma(src, len)) / ta.stdev(src, len)
`,
      },
    ],
  },
);

Registry keys are "Publisher/Lib/Version" or { user, lib, version }. Exported functions, UDTs (type), enums, and methods resolve through the alias. Versions match exactly; transitive imports resolve (depth cap 32) with cycles rejected; export-constraint violations (e.g. plot inside an export) are compile errors. Imported symbols are inline-merged, so the two backends stay byte-for-byte identical. An alias equal to a builtin namespace (e.g. ta) is rejected — piner does not implement TradingView's builtin-namespace extension.

Loading libraries from the filesystem (Node)

The core compile() is pure and browser-safe (no I/O). For Node/CLI/server use, the optional @heyphat/piner/node entry point builds a registry from .pine files on disk — so you don't assemble it by hand. It's never bundled into the browser build.

import { loadLibraryDir, compile } from '@heyphat/piner/node';

// Scans <root>/<publisher>/<lib>/<version>.pine  (mirrors the import identity):
//   pine-libs/PineCoders/AllTimeHighLow/1.pine → "PineCoders/AllTimeHighLow/1"
const libraries = loadLibraryDir('./pine-libs');
const compiled = compile(source, { libraries });

loadLibraryManifest('libs/manifest.json') is also available for non-conventional layouts (a JSON map of "Publisher/Lib/Version" → source-file path). The identity comes from the path, not the file's library("…") title; multiple <version>.pine files coexist.

Async / lazy resolution (HTTP, CDN, large trees)

When sources live behind async I/O (an HTTP CDN, a database) or in a large on-disk tree you don't want to scan eagerly, compileAsync(src, { resolveLibrary }) walks the import graph and fetches ONLY the libraries actually imported (transitively), then calls the pure compile():

import { compileAsync } from '@heyphat/piner';

const compiled = await compileAsync(source, {
  resolveLibrary: async ({ canonical }) => {
    const res = await fetch(`https://cdn.example.com/pine/${canonical}.pine`);
    return res.ok ? await res.text() : undefined; // undefined ⇒ missing-library error
  },
});

The provider may be sync or async. Node's fsLibrarySource('./pine-libs') (from @heyphat/piner/node) is a ready-made lazy provider that reads only the single <publisher>/<lib>/<version>.pine files that are imported. compile() itself stays synchronous and pure — compileAsync just gathers sources first (see resolveLibraryClosure for the standalone gatherer).

Contributing

Contributions are welcome — bug reports, fixes, new built-in coverage, and docs. Please read CONTRIBUTING.md (especially the clean-room policy) and the Code of Conduct first.

License

GNU AGPL-3.0 © Phat Huynh.

Piner is a clean-room reimplementation from public TradingView documentation. No third-party Pine engine code is used or copied.