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

@node-api-toolkit/save-token

v1.0.0

Published

A small utility to write your tokens to the file system to easily retrieve later

Downloads

5

Readme

Save Token

A small utility to write your tokens to the file system to easily retrieve later

Installation

yarn add @node-api-toolkit/save-token

Usage

There are two modes of usage:

Save to default file location using a tokenIdentifier

You can easily save a token to the default storage location (in /tmp) and access it using a unique identifier.

Examples of identifiers should look something like MY_APP_DROPBOX_API_TOKEN_USER_123. Remember to make it as specific as possible because it may conflict with other tokens that are using this tool. As a rule of thumb include:

  • Name of your app
  • Name of the token
  • User ID/Email who the token belongs to

To save:

import { saveToken } from "save-token";

await saveToken({
  tokenIdentifier: "TEST_TOKEN",
  token: "I_AM_A_TOKEN"
});

To retrieve do:

import { getToken } from "save-token";

const token = await getToken({
  tokenIdentifier: "TEST_TOKEN"
});

Save token to custom file

You can also specify a custom location for your file. This is useful if you have a existing storage directory.

To save:

import { saveToken } from "save-token";

await saveToken({
  fileName: "/my/custom/location/TEST_TOKEN",
  token: "I_AM_A_TOKEN"
});

To retrieve do:

import { getToken } from "save-token";

const token = await getToken({
  fileName: "/my/custom/location/TEST_TOKEN"
});