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

bs-elm-es6

v0.1.1

Published

a stand-alone package for interoperation between Elm and BuckleScript compatible with es6 modules.

Downloads

1

Readme

bs-elm-es6

a package for interoperation between Elm and BuckleScript compatible with ES6 modules

Philosophy

All respect to the existing bs-elm project, but since it required a script bundler, I decided to write my own that doesn't require a bundler to fit my use case.

Installation

npm install bs-elm-es6 in your console and then add "bs-elm-es6" to your bs-dependencies.

Usage

  1. (Optional) Expose the module in your Index.re, like so: open ElmES6;

  2. Define your ports type as a record, where each field is either a sendable of a type or a subscribable of a type. For example:

     type ports = 
     {
       toElm: Elm.sendable(string),
       fromElm: Elm.subscribable(string)
     };
  1. Get your target node and initialize your app. For example:
    [@bs.val][bs.scope "document"]
    external getElementById: string => Dom.element = "getElementById";
    let app: Elm.app(ports) = 
      Elm.Main.init({ node: getElementById("elm-target") });
  1. Use your ports. There are two ways to do this.

The BuckleScript-y Way to use ports.

bs-elm-es6 exposes methods Elm.send('model, sendable('model)) and Elm.subscribe(('model => unit), subscribable('model)).

You can pipe into these methods like so:

app.ports.toElm -> Elm.send("Hello, from ReasonML.");
app.ports.fromElm -> Elm.subscribe(str => Js.log(str));

I imagine this is the primary way most users will interact with this package.

The JavaScript-y Way to use ports.

bs-elm-es6 also exposes a less-idiomatic-to-BuckleScript way to interact with Elm ports. That is, sendable('model) and subscribable('model) are both records with a function-valued field.

That is, you can literally call the object method directly in ReasonML like: app.ports.toElm.send("Hello, from ReasonML");

This is kind of a cringe-y hack and I don't imagine it will be widely used, but it may be useful if you're coming from the JavaScript/Elm world or if you want a faster refactor from JavaScript to Reason. (Plus, I really just wanted to see if something like this would work, and it does.)

Example

There's a fully functioning, minimal example at https://elmandbucklescript.bitbucket.io which includes one incoming and one outgoing port. Let me know if you have any questions.

For further reading

I strongly recommend you check out my catch-all documentation on my projects. It describes how to get in touch with me if you have any questions, how to contribute code, coordinated disclosure of security vulnerabilities, and more. It will be regularly updated with any information I deem relevant to my side projects.

Most of all, feel free to get in touch! I'm delighted to hear suggestions or field questions.