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

neru-alpha

v5.1.0

Published

[![npm version](https://img.shields.io/npm/v/sdk-name.svg)](https://www.npmjs.com/package/neru-alpha) [![Coverage Status](https://coveralls.io/repos/github/your-username/sdk-name/badge.svg?branch=master)](https://coveralls.io/github/your-username/sdk-name

Downloads

4,393

Readme

NERU-SDK

npm version Coverage Status

Table of Contents

About

A Node.js SDK for NeRu platform for interacting with Vonage API.

To get started, please visit our documentation.

Installation

npm install neru-alpha --save

Development

Pre-Requisites

  • Node.js 14x or higher
  • NPM 6x or higher
  • Git

Clone the repository and install the dependencies.

git clone [email protected]:nexmoinc/neru-sdk.git

cd neru-sdk/nodejs

npm install

Branching

This project follows the Git Flow branching model. The master branch always reflects a production-ready state while the latest development is taking place in the develop branch.

To contribute to the project, create a new feature branch off of the develop branch and merge back into develop when complete. Do not merge directly into master.

Hot fixes should be created as a branch off of master and merged into both master and develop.

Branch naming convention: <jira-task-id>__<short-description>

Build

To build the project, run the following command:

cd nodejs

npm run build

It will generate the SDK in the nodejs/dist folder.

📦dist
 ┣ 📂cjs          # CommonJS build
 ┃ ┗ neru.js     # Entry point
 ┗ 📂esm          # ES Module build
 ┃ ┗ neru.js     # Entry point

Generating SDKs from the source code

Pre-Requisites

Python SDK

To generate the Python SDK, run the following command:

pilo -l=python --input=nodejs/src --output=python/src --ignore='nodejs/src/bridge.ts' --namespace=nerualpha --clean=true

cp templates/python/* python/src/nerualpha

C# SDK

To generate the C# SDK, run the following command:

pilo -l=csharp --input=nodejs/src --output=dotnet --ignore='nodejs/src/bridge.ts' --namespace=Vonage.Neru --clean=true

cp templates/dotnet/* dotnet/Vonage.Neru

Releasing

  • Create a release branch from develop branch, e.g release/v1.0.0
  • Run tests locally by typing npm test in the nodejs folder
  • Generate Python SDK by running npm run generate:python. This will generate the Python SDK from nodejs src code and copy it to the python folder
    • Test the Python SDK by running smoke tests against the source code
  • Bump package version in nodejs and python SDKs manually or by running npm bumpVersion:[ major | minor | patch ] (requires python3, pip3, bumpver)
  • Update CHANGELOG.md in nodejs folder
  • Create a new release from the repository
    • Specify the tag name which is the version number e.g v1.0.0
    • Add a release title e.g v1.0.0
    • Add a description for the release
    • Publish the release. This will create a new release on GitHub and starts the release process using GitHub Actions for both nodejs and python SDKs