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

import.js

v0.1.1

Published

A dynamic import() polyfill

Downloads

13

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

webreflectionwebreflection

Keywords

importdynamicpolyfill

Readme

import.js

A dynamic import() polyfill.

Features

  • [x] compatible with native ES2015 modules
  • [x] compatible with native import ... from ...
  • [x] compatible with common native export ... expressions
  • [x] compatible with Babel transpiled ES2015 modules
  • [x] compatible with relative paths
  • [x] compatible with absolute paths

Usage

<!doctype html>
<!-- literally anything you need before -->
<script
    async
    src="import.js"
    data-main="js/main.js"
></script>
  • the src should point to import.js or its min.js version
  • the data-main should point to your module entry point
  • feel free to use or not deferred or async to delay execution
  • all modules will be loaded through XHR to avoid the need of a fetch polyfill
  • however, you can add any polyfill you need upfront

Use https://unpkg.com/import.js@latest as source if you'd like to use a CDN service.

Live test based on this folder.

You can test native ES2015 module export too. It requires a compatible browser (today any modern WebKit would do).