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

@astronautlabs/is04

v0.0.6

Published

AMWA IS-04 NMOS Discovery and Registration

Downloads

39

Readme

@/is04

npm CircleCI

📜 NMOS IS-04
AMWA IS-04 NMOS Discovery and Registration Specification (Stable)

📺 Part of the Astronaut Labs Broadcast Suite
@/is04 | @/is05 | @/is07 | @/rfc8331 | @/rtp | @/scte104 | @/scte35 | @/st2010 | @/st291

Alpha Quality
This library is still in development and is subject to change


Implementation of AMWA's NMOS IS-04 standard for Discovery and Registration. Currently covers the Node API and related functionality of the standard (ability to implement a Node, ability to register and query such a Node).

Passes the IS-04 suites of the NMOS Test tool.

Usage

npm install @astronautlabs/is04

Then add IS04Module to your app, mount NodeApi, inject RegistryService and get started:

import { WebService } from "@alterior/web-server";
import { IS04Module, NodeApi, RegistryService } from "@astronautlabs/is04";

@WebService({
    imports: [ IS04Module ],
    server: {
        // ...

        // You should make sure to implement CORS in some way
        // as it is required by the specification
        middleware: [ CORS ], // see below
        
        // You should ensure that 404s conform to the NMOS 
        // API style:
        defaultHandler: ev => {
            ev.response.status(404).json(<Error>{
                code: 404,
                debug: 'not-found',
                error: 'The resource was not found'
            });
        }
    }
})
class MyService {
    constructor(
        private registry : RegistryService
    ) {
    }

    @Mount() nodeService : NodeApi;

    async altOnInit() {
        await this.registry.init();

        this.registry.node.label = 'My Node';
        this.registry.node.description = 'This is my NMOS node';
        // ...and otherwise customize this.registry.node

        // Add your initial resources
        await this.nodeService.addDevice({ /* ... */ });
        await this.nodeService.addSource({ /* ... */ });
        await this.nodeService.addSender({ /* ... */ });
        await this.nodeService.addReceiver({ /* ... */ });

        // Once all your initial resources are added, call .register()
        // to find the registration service and register them
        await this.nodeService.register();

        // After registering, you can continue adding resources
        // and they will be automatically registered with the 
        // registry

        await this.nodeService.addReceiver({ /* ... */ });
    }
}

Add CORS

To be spec-compliant, you must implement CORS for this API. You should attach a middleware that handles CORS to your requirements. The following example opens CORS broadly, though this may not be suitable for a production deployment.

function CORS(req : express.Request, res : express.Response, next : Function) {
    res
        .header('Access-Control-Allow-Origin', req.header('origin') || '*')
        .header('Access-Control-Allow-Methods', 'GET, PUT, POST, PATCH, HEAD, OPTIONS, DELETE')
        .header('Access-Control-Allow-Headers', 'Content-Type, Accept')
        .header('Access-Control-Max-Age', '3600')
    ;
    next();
}

@WebService({
    server: [
        middleware: [ CORS ]
    ]
})
class MyService {
    nodeService : NodeService;
}