Ready to take your JavaScript development to the next level? Meet npm Enterprise - the ultimate in enterprise JavaScript. Learn more »

elm-phoenix-websocket-ports

1.0.1 • Public • Published

Elm Phoenix Websocket Ports Build Status

Communicate with a Phoenix Framework application via Websocket.

Quick Start

1. Install via NPM

$ npm install --save elm-phoenix-websocket-ports

2. In elm-package.json, import Ports/Websocket.elm

Add node_modules/elm-phoenix-websocket-ports/lib/elm to your source-directories:

// elm-package.json
 
{
    // ...
 
    "source-directories": [
        "../../node_modules/elm-phoenix-websocket-ports/lib/elm", // Exact path to node_modules may be different for you
        "./"
    ],
 
    // ...
}

3. Use it in your Elm code

type Msg
  = WebsocketReceive (String, String, Json.Decode.Value)
 
 
init =
  ( someModel
  , Ports.Websocket.websocketListen ("search", "receive_results")
  )
 
 
subscriptions model =
  Ports.Websocket.websocketReceive WebsocketReceive
 
 
update msg model =
  case msg of
    WebsocketReceive ("search", "receive_results", payload) ->
      case Json.Decode.decodeValue searchResultsDecoder payload of
        Ok searchResults ->
          -- Do something with searchResults

4. Register your Elm app in JavaScript

Using Elm Router

var phoenix = require('phoenix');
var socketAddress = '/socket';
 
var websocketPorts = require('elm-phoenix-websocket-ports')(phoenix, socketAddress);
elmRouter.start(Elm, [websocketPorts]);

Without Elm Router

var phoenix = require('phoenix');
var socketAddress = 'ws://website.com/ws';
var websocketPorts = require('elm-phoenix-websocket-ports')(phoenix, socketAddress);
 
var myElmApp = Elm.MyElmApp.embed(document.getElementById('my-elm-app-container'));
 
websocketPorts.register(myElmApp.ports);

Factory Function API

Notice that the module itself is a factory function with this signature:

function websocketPorts(phoenix, socketAddress, [opts, [topicProvider]])

The last two parameters are optional:

  • opts is an object containing the options passed into the phoenix.Socket constructor, as documented in the JSDoc of the code.
  • topicProvider is a function that transforms topic strings.

In practice, topicProvider would be used to do something like appending a user ID to a topic:

function websocketTopicProvider(topic) {
  if (user.id) {
    return topic + ":" + user.id;
  }
 
  return topic;
}

Although it'd probably be a better pattern to pass in an access token to the socket and derive the user from the token. opts can be used to achieve this:

var websocketPorts = require('elm-phoenix-websocket-ports')(
  phoenix,
  socketAddress,
  {params: {token: ACCESS_TOKEN}}
);

phoenix

This is the Phoenix Framework JavaScript client. Instead of making Phoenix a dependency of this NPM module, we require it to be injected.

We do this to avoid bloating your bundle by double-importing the Phoenix client, since mix phoenix.new sets up package.json to import the Phoenix JavaScript client from a relative path in the code repository.

socketAddress

This is the path to your socket endpoint. It can be a relative or absolute path. For example:

/ws
ws://example.com/socket
wss://www.mysite.com/socket_endpoint

API Reference

View the full API reference here.

Questions or Problems?

Feel free to create an issue in the GitHub issue tracker.

install

npm i elm-phoenix-websocket-ports

Downloadsweekly downloads

50

version

1.0.1

license

MIT

homepage

github.com

repository

Gitgithub

last publish

collaborators

  • avatar
Report a vulnerability