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

elm-ext-package

v0.1.7

Published

Tool to use external packages not published in package.elm-lang.org

Readme

elm-ext-package V 0.1.7

Tool to use external packages not published in package.elm-lang.org.

Installing

Use npm to install it globally.

$ npm install -g elm-ext-package

After that you can use the command elm-ext-package

Introduction

elm-make relies on the information in elm-package.json to compile. If you are using modules not published in package.elm-lang.org you might be doing one of these:

  • Adding the source folder of the external packages to your source-directories array in elm-package.json
  • Copying the source of the external packages to your project directory
  • ... other ways ...

But if you use native code (as in import Native.xxx) you might find difficult to make it working between projects, mostly due to the namespace.

Also, Elm packages using native javascript code, effect or port modules cannot be published on package.elm-lang.org using the normal procedures, it must pass a native review and conform to some guidelines.

Last but not least, you might not want (or not allowed by management) to publish your modules publicly.

Instead of copying the code, or linking to it, it would be so much better if you could have packages like the official ones and use in multiple projects. This can be done manually modifying some files (like elm-package.json), but it makes you unable to download or update official packages until you remove your changes.

This tool may be able to help you in these cases.

Usage

Example project elm-ext-package-example

In your project, you must add the file elm-ext-package.json with a dependencies field like the one in elm-package.json, example:

{
    "dependencies": {
        "aaronps/elm-arraylist": "1.0.0 <= v < 2.0.0"
    }
}

You must copy or download the ext-packages to the folder elm-stuff/ext-packages under your project, following the previous example, the final location would be elm-stuff/ext-packages/aaronps/elm-arraylist.

Now you are almost ready, there are 2 things to do:

  • Compiling your project with the ext-modules
  • Downloading or updating elm packages from package.elm-lang.org

Compiling with ext-modules

You need to activate, or apply the changes to the files, use:

$ elm-ext-package apply

elm-ext-package 0.1.5
Enabling Ext Packages
Copying aaronps/elm-arraylist version 1.0.0 to packages

Now you can work with the external modules, just use them like they were standard ones (import Some.Module).

Downloading standard packages

You need to deactivate on revert the changes done to the files, use:

$ elm-ext-package revert

elm-ext-package 0.1.5
Disabling Ext Packages

Now you can elm-package install the normal modules.

Creating a package

Packages are created the same way as any Elm package or application is done, there is no need to do anything special, just do it.

Missing functionality

  • Downloading of packages: currently you must download or copy the packages yourself, this might change in the future.

  • Dependency checks: currently this tool is not checking any dependency, if the packages depends on others (either standard packages or ext-packages) you must add the dependencies yourself, this might change in the future.

  • Listing of ext-packages: there is no centralized location for the ext-packages. You must either have it locally or at least know its repository address, this might change in the future.