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

@datastripes/forecast

v0.2.6

Published

WebAssembly time-series forecasting engine with drop-in components for React, Vue, Angular, and vanilla Custom Elements, shipped as one package with one subpath per framework.

Readme

@datastripes/forecast

Time-series forecasting engine with drop-in UI components for React, Vue, Angular, and vanilla Custom Elements, in one npm package.

npm install @datastripes/forecast

| Import path | Contents | Needs | |---|---|---| | @datastripes/forecast | Core engine: executeForecast, auto column discovery, licensing client, all types | nothing | | @datastripes/forecast/react | DatastripesForecast and companion components, useWasmForecast hook | react, react-dom ^19 | | @datastripes/forecast/vue | DatastripesForecast and companion components, useWasmForecast composable | vue ^3.4 | | @datastripes/forecast/angular | Standalone components (DatastripesForecastComponent, …), Angular Package Format | @angular/core, @angular/common ^18 || ^19 | | @datastripes/forecast/elements | <datastripes-forecast-studio> and companion Custom Elements | nothing |

The UI frameworks are optional peer dependencies, so installing the package never pulls one in. Every framework entry re-exports the core API, and all entries share one copy of the core engine at runtime.

Build

npm run build (from this folder, or npm run build -w @datastripes/forecast from the repo root) wipes dist/ and runs three steps:

  1. build:core, tsup: the root, /react, and /elements entries (ESM + CJS + .d.ts, with the shared engine split into a common chunk), plus a self-contained IIFE build at dist/elements/index.global.js for plain <script> tags.
  2. build:vue, Vite library mode with @vitejs/plugin-vue and vite-plugin-dts, into dist/vue/. The Vue sources import the core relatively; the build rewrites that import to @datastripes/forecast and keeps it external.
  3. build:angular, ng-packagr on src/angular/ng-package.json, into dist/angular/ (Ivy partial compilation, FESM2022 bundle at dist/angular/fesm2022/datastripes-forecast-angular.mjs). It imports the core as @datastripes/forecast, so it must run after step 1.

Why the Angular entry has its own package.json

ng-packagr derives an entry point's module id from where its ng-package.json sits relative to the primary package that ng-packagr itself builds, and it deletes and owns its primary dest. Here the primary entry is built by tsup, not ng-packagr, so src/angular/ is set up as the ng-packagr project: src/angular/package.json names it @datastripes/forecast/angular (private, never published on its own) and ng-package.json writes to ../../dist/angular. The result matches APF secondary-entry-point output, and the root package.json's "./angular" export points at it.

Angular 18.2, ng-packagr 18.2, and TypeScript ~5.4 are pinned as dev dependencies of this package because Angular 18's compiler does not support newer TypeScript.

Checks

  • npm run lint: vue-tsc over everything except src/angular, then tsc over src/angular with the Angular decorator settings.
  • Tests run from the repo root with npm test (vitest).