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

@emilgroup/process-manager-sdk-node

v1.8.0

Published

OpenAPI client for @emilgroup/process-manager-sdk-node

Downloads

161

Readme

Emil Process Manager SDK for Nodejs

This TypeScript/JavaScript client utilizes axios. The generated Node module can be used with Nodejs based applications.

Language level

  • ES5 - you must have a Promises/A+ library installed
  • ES6

Module system

  • CommonJS
  • ES6 module system

Although this package can be used in both TypeScript and JavaScript, it is intended to be used with TypeScript. The definition should be automatically resolved via package.json. (Reference). For more information, you can go to Emil Api documentation.

Consuming

Navigate to the folder of your consuming project and run one of the following commands:

npm install @emilgroup/[email protected] --save

or

yarn add @emilgroup/[email protected]

And then you can import WorkflowsApi.

import { WorkflowsApi } from '@emilgroup/process-manager-sdk-node'

const workflowsApi = new WorkflowsApi();

Credentials

To use authentication protected endpoints, you have to first authorize. To do so, the easiest way is to provide a configuration file under ~/.emil/credentials with the following content:

[email protected]
emil_password=XXXXXXXXXXXXXX

It is also possible to provide environment variables instead:

export [email protected]
export EMIL_PASSWORD=XXXXXXXXXXXXXX

Base path

To select the basic path for using the API, we can use two approaches. The first is to use one of the predefined environments, and the second is to specify the domain as a string.

import { WorkflowsApi, Environment } from '@emilgroup/process-manager-sdk-node'

const workflowsApi = new WorkflowsApi();

// Allows you to simply choose environment. It will usually be Environment.Production.
workflowsApi.selectEnvironment(Environment.Production);

// For advanced users, use the custom baseUrl of the website you need to connect to.
workflowsApi.selectBasePath('https://my-custom-domain.com');

Example

Here is a basic functionning example:

async function listWorkflows(): Promise<Void> {
    try {
        const workflowsApi = new WorkflowsApi();

        await workflowsApi.initialize(); // should be called only once per Api.

        const { data: { items } } = await workflowsApi.listWorkflows();

        console.log(items);
    } catch(error) {
      // process error
  }
}