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 🙏

© 2024 – Pkg Stats / Ryan Hefner

elm-ts-interop

v0.0.8

Published

## How It Works

Downloads

589

Readme

elm-ts-interop Community Edition

How It Works

The ports and flags in an Elm app (also called JS interop) have a shape to them. You can write that shape out with a TypeScript type to make sure the types match up between your Elm and TypeScript code. You could write a definition like this:

export interface ElmApp {
  ports: {
    interopFromElm: PortFromElm<FromElm>;
    interopToElm: PortToElm<ToElm>;
  };
}

export type FromElm =
  | { tag: "reportError"; data: { message: string; name: string } }
  | { tag: "tryLogIn"; data: null };

export type ToElm =
  | {
      tag: "onAuthenticated";
      data: { isPro: boolean; user: { avatarUrl: string } };
    }
  | { tag: "onNewGeneratedElm"; data: string };

export type Flags = null;

export namespace Main {
  function init(options: { node?: HTMLElement | null; flags: Flags }): ElmApp;
}

export as namespace Elm;

export { Elm };

export type PortFromElm<Data> = {
  subscribe(callback: (fromElm: Data) => void): void;
};

export type PortToElm<Data> = { send(data: Data): void };

This is great because now we can safely wire up our Elm application and use ports to send and receive data! But if we wrote it by hand, then it's error prone and likely to get out of date.

That's exactly what elm-ts-interop is designed to help with. This is the workflow to generate a TypeScript Declaration similar to the example above:

  • You maintain a file InteropDefinitions.elm with Encoders/Decoders for your Flags and Ports
  • These Encoders/Decoders use elm-ts-json so they have type information that lets elm-ts-interop sync them to a TypeScript Declaration
  • Run the elm-ts-interop command-line tool to generate types from your Ports and Flags in InteropDefinitions.elm

Getting Started

Run npx elm-ts-interop init from the root of your Elm project to copy an initial InteropDefinitions.elm and InteropPorts.elm file. From there, npx elm-ts-interop will generate your TypeScript Declaration file.

More docs at elm-ts-interop.com/setup.