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

@useupup/core

v3.3.5

Published

Headless, framework-agnostic file-upload engine powering the upup uploader — file state, upload pipeline (compression, HEIC, web-worker offload), cloud-drive sources, i18n, and theming.

Readme

@useupup/core

The headless engine behind upup: file state and upload orchestration, the upload pipeline (image compression, HEIC decode, web-worker offload), cloud-drive plugins (Google Drive, OneDrive, Dropbox, Box), theming, and ICU i18n. It has zero framework dependencies and powers every @useupup/* UI package.

Install

Most consumers should install a framework package instead — @useupup/react, @useupup/vue, @useupup/svelte, @useupup/angular, @useupup/vanilla, or @useupup/preact — which bundle this engine and render a ready-made UI. Install @useupup/core directly only to drive uploads headlessly or to build your own UI binding.

npm i @useupup/core

Headless usage

import { UpupCore } from '@useupup/core'

const core = new UpupCore({
    provider: 'aws',
    uploadEndpoint: '/api/upload-token',
})

UpupCore owns the file/progress state, the upload lifecycle, and the cloud-drive plugins. See the docs for the full event and method surface.

Errors

Upload failures are typed. Catch UpupError and branch on its stable UpupErrorCode; the concrete subclasses (UpupValidationError, UpupNetworkError, UpupStorageError, UpupAuthError, UpupQuotaError, UpupConfigError) let you narrow further.

import { UpupError, UpupErrorCode } from '@useupup/core'

function isRetryable(err: unknown): boolean {
    return err instanceof UpupError && err.code === UpupErrorCode.NETWORK_ERROR
}

StorageProvider enumerates the supported storage providers (StorageProvider.AWS, StorageProvider.CloudflareR2, StorageProvider.MinIO, and more).

Entry points

The main @useupup/core entry is a curated allow-list of stable exports (the UpupCore engine, the drive plugins, the UpupError taxonomy — UpupError plus its typed subclasses and the UpupErrorCode enum — the locale bundles, and the theme presets). Advanced, deep-import-only subpaths are also published:

  • @useupup/core/internal — implementation internals (managers, orchestrator, controllers)
  • @useupup/core/contracts, @useupup/core/i18n, @useupup/core/theme, @useupup/core/strategies
  • @useupup/core/pipeline and @useupup/core/steps/* (hash, heic, exif, compress, thumbnail)

Heavy capabilities (HEIC decode, resumable/tus uploads) load lazily via these subpaths, so they never weigh down the main entry.

Links

License

MIT