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-ffi

v1.0.0

Published

elm-ffi polyfill

Readme

elm-ffi

  • THIS USES HACKS: I decline all responsabilities.
  • Calling JS from Elm is a bit of a controversy. This is not recognized as a standard practice among the Elm community. Favourise using ports and WebComponents, if you use a lot of JS in Elm maybe what you need is JS?
  • You can find a previous version of this using Elm's Kernel in the Kernel branch of this repo, this version is a complete rip-off from joakin
  • Do not forget: JS code within Elm is not touched by JS compilers/build tools.

This should work where modern javascript works: browsers, node, deno, bun...

Setup

Install both Elm & JS dependencies:

elm install Warry/elm-ffi
npm install Warry/elm-ffi --save

Apply the polyfill before initialiazing your Elm app:

import 'elm-ffi' // just import it, and that's it.
import { Elm } from './Main.elm'
let app = Elm.Main.init(<your code>)

Usage

Read global values from javascript

read : JsCode -> Value

Create and call asynchronous javascript functions from Elm

function : List ( String, params -> Value ) -> JsCode -> params -> Task Error Value

Examples

import FFI
import Json.Encode exposing (Value)
import Json.Decode exposing (Decoder)
import Task

{-
when FFI.read fails, value is undefined (not readable by elm/json)
-}
language : String
language =
    FFI.read "return window.navigator.language"
    |> Decode.decodeValue Decode.string
    |> Result.withDefault "en"

{-
it's good practice to declare functions using only the first two parameters,
leaving the given function parameter to currying.
this way function code is cached properly, and execution will be fast.
-}
fetchJson : { url: String } -> Task Error Value
fetchJson =
    FFI.function
        [ ( "url", .url >> Json.Encode.string )
        ]
        """
        let res = await fetch(url)
        if (!res.ok) throw res.statusText
        return await res.json()
        """

fetchUser : Cmd (Result String User)
fetchUser =
    fetchJson { url = "/api/user" }
        |> FFI.decode decodeUser
        |> Task.mapError FFI.errorToString
        |> Task.perform identity

see example/

How fast is it?

Faster than eval(), the little overhead consists in converting parameters' values to pojo then passing them to the function using the hack. If your functions are declared at the top level then they are pre-compiled on load.

How safe is it?

  • JS code is guaranteed to run within a Task meaning that your Elm runtime still can't break.
    • Effects are still managed, creating a JS function in Elm won't do anything until the Cmd is ran.
  • JS code runs in isolation, meaning that you can only access function arguments and global references.