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

fin-utils

v1.1.1

Published

Shared utilities for Fin.

Downloads

22

Readme

fin-utils

Shared utilities for Fin.

NPM Build Status JavaScript Style Guide

Install

npm install fin-utils

Usage

parseFaasIdentifier

const finUtils = require('fin-utils')

// parses any FaaS identifier (see the FaaS format below for more examples)
const parsedInfo = finUtils.parseFaasIdentifier('username/projectName.serviceName@01234567')

if (!parsedInfo) {
  console.error('invalid identifier')
} else {
  const { projectId, serviceName, deploymentHash, version } = parsedInfo

  if (serviceName) {
    console.log(`${projectId}.${serviceName}@${deploymentHash || version}`)
  } else {
    console.log(`${projectId}@${deploymentHash || version}`)
  }
}

validators

const finUtils = require('fin-utils')
const { validators } = finUtils

validators.email('[email protected]') // true
validators.email('foo') // false

validators.username('transitive-bullshit') // true
validators.username('foo$86') // false

validators.password('password') // true
validators.password('a') // false (too short)

validators.projectName('hello-world') // true
validators.projectName('%') // false

validators.deploymentHash('abc123yz') // true
validators.deploymentHash('ABCdefGHIjkl') // false

validators.project('username/goodProject') // true
validators.project('username\bad%project') // false

validators.deployment('username/goodProjectName@abc123yz') // true
validators.deployment('username/bad%project%20name@ZZ') // false

FaaS Identifier Format

The most general FaaS identifier fully specifies the deployment and service name.

It may include an optional URL prefix such as http://localhost:5000/1/call/ in development or https://api.functional-income.com/1/call/ in production. The parsed result will be the same with or without the full URL prefix.

username/projectName.serviceName@01234567  // explicitly identify a specific deployment (may not be published)
username/projectName.serviceName@latest    // explicitly identify the latest published deployment
username/[email protected]     // explicitly identify a the published deployment with a specific version
username/projectName.serviceName           // implicitly identify the latest published deployment

If no serviceName is specified, it is assumed that the deployment only has a single service and errors if this is not the case.

username/projectName@01234567
username/projectName@latest
username/[email protected]
username/projectName

Omitting username

You may optionally leave off the username/ prefix when referring to your own projects and deployments via the dev CLI.

projectName@01234567
projectName@latest
[email protected]
projectName

An example of this for the hello-world project would look like:

# view all deployments for the authenticated user's hello-world project
fin ls hello-world

This would be equivalent to:

# view all deployments for my-user-name/hello-world project
fin ls my-user-name/hello-world

Related

  • fin - Fin is the easiest way to launch your own SaaS.
  • fts - TypeScript standard for rock solid serverless functions.

License

MIT © Travis Fischer