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 🙏

© 2025 – Pkg Stats / Ryan Hefner

portatext

v1.6.1

Published

Official client for the PortaText API

Readme

License npm version js-standard-style

Build Status Coverage Status Code Climate Issue Count

node-sdk

Official NodeJS Client for the PortaText API.

Documentation

  • Autogenerated documentation for this source can be found in the doc directory.
  • The endpoint tests should also serve as good doucmentation on how to use the API.
  • General PortaText documentation (including the REST API) can be found at the PortaText wiki.

Installing

Add this library to your package.json configuration:

  "dependencies": {
    "portatext": "latest"
  }

Basic use

Getting a client instance

The first thing is to get a Client instance, for example the Curl implementation:

var portatextMod = require('portatext');
var portatext = new portatextMod.ClientHttp();

(Optional) Set your logger

You can optionally set a Console compatible logger:

portatext.setLogger(console);

By default, the client will use the NullLogger.

Authenticating

You can authenticate to the endpoints by using your API key or your username/password. This translates to either doing this:

portatext.setApiKey(apiKey);

Or this:

portatext.setCredentials(username, password);

When you specify a username and password instead of an api key, the sdk will automatically login and get a session token when needed.

Using the endpoints

All the API commands can be found in the command/api directory. The client offers a way to instantiate them by just calling them by their name.

Quick example

As an example, to create a template, you would do:

client
  .templates()                       // Get an instance of the Templates endpoint.
  .text("The text of my template")
  .description("My first template")
  .name("template1")
  .post()                            // Call the Templates endpoint with a POST.
  .then(function (result) {
    // Handle result...
  })
  .catch(function (err) {
    // Handle error...
  });

To get a template by id:

client.templates().id(45).get().then(function (result) { .... });

Or, to get all the templates:

client.templates().get().then(function (result) { .... });

The result

Calling an endpoint will return a Promise. On fulfillment, a result object is returned (see below for how to handle it). On rejection, you can get a string or a result object (in case the request was made but the server returned one or more errors in its response, for example if a field was missing or different than what was expected).

Testing for success

if (result.success) {
  ...
}

Getting error strings back from the server

if (result.errors) {
  result.errors.forEach(function (error) {
    ...
  });
}

Getting data back from the server

if (result.success) {
  var data = result.data;
}

Developers

This project uses standard npm scripts. Current tasks include:

  • test: Runs Mocha tests.
  • jsdoc: Runs JSDoc3.
  • eslint: Runs ESLint.
  • coverage: Runs the tests and then Instanbul to get a coverage report.
  • build: This is the default task, and will run all the other tasks.

Running a phing task

To run a task, just do:

npm run build

Contributing

To contribute:

  • Make sure you open a concise and short pull request.
  • Throw in any needed unit tests to accomodate the new code or the changes involved.
  • Run npm run build and make sure everything is ok before submitting the pull request (make eslint happy).
  • Your code must comply with the Javascript Standard Style, ESLint should take care of that.
  • If your code is accepted, it will belong to PortaText and will be published under the Apache2 License.

License

The source code is released under Apache 2 License.

Check LICENSE file for more information.