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 🙏

© 2025 – Pkg Stats / Ryan Hefner

import-optional

v2.0.0

Published

A tiny library to help deal with optional dependencies without the hassle of needing to `.catch` for dynamic imports

Readme

import-optional

A tiny library to help deal with optional dependencies without the hassle of needing to .catch for dynamic imports

Usage

Array

// some-config.js
import { optional } from 'import-optional';

// import your optional dependencies
const optionalPlugins = await Promise.all([
  optional(import('my-dependency-1'), m => m.default),
  optional(import('my-dependency-2'), m => m.default),
  // Importing is still done manually for type safety
]);

// then use them as if you did `import * as myDependency from 'my-dependency'`:
export default {
  plugins: [
    plugin1,
    plugin2,
    // ...
    ...optionalPlugins
  ]
}

Object

// some-config.js
import { importOptional } from 'import-optional';

// import your optional dependencies
const optional = await importOptional({
  myDependency: import('my-dependency')
  // Importing is still done manually for type safety
});

// then use them as if you did `import * as myDependency from 'my-dependency'`:
optional.myDependency?.default('some default exported function');

Object with fallbacks

It's possible to define fallbacks that trigger per-dependency, just like with regular .catch:

// some-config.js
import { importOptional } from 'import-optional';

const optional = await importOptional({
  myDependency: import('my-dependency')
}, {
  myDependency: (error) => {
    console.error('Oh no... Anyway');
    return import('my-alt-dependency');
  }
});

optional.myDependency?.default('some default exported function');

Reasoning

This is a tiny library, but it simplifies the mental gymnastics needed to work with multiple optional npm dependencies or just many imports that may fail for some reason.

It is rather redundant and opinionated, but makes the code look nice.

My personal reason for this came from needing to use optional dependencies in vite config plugins:

import { defineConfig } from 'vite';

// This breaks the config if the dependency is missing
import * as somePlugin from 'some-optional-dep';

// - Very tiring to do for every dependency
// - Not very idiomatic
// - Looks chaotic in bulk: each import spans over multiple lines
const somePlugin = await import('some-optional-dep')
  .catch(() => null);

export default defineConfig({
  // Imagine a couple hundred lines of configuration here...

  plugins: [
    // Not clear that this is optional at all
    somePlugin.default()
  ]
})

Now, with optional:

import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [
    // Clear that it's an optional dependency
    await optional(import('some-optional-dep'), m => m.default())
  ]
})