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 🙏

© 2026 – Pkg Stats / Ryan Hefner

easy-functions

v1.0.1

Published

Using functions-framework to make easy functions

Readme

Easy to create API

base on @google-cloud/functions-framework

Configure

| Command-line flag | Environment variable | Description | | ------------------ | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | --port | PORT | The port on which the Functions Framework listens for requests. Default: 8080 | | --target | FUNCTION_TARGET | The name of the exported function to be invoked in response to requests. Default: function | | --signature-type | FUNCTION_SIGNATURE_TYPE | The signature used when writing your function. Controls unmarshalling rules and determines which arguments are used to invoke your function. Default: http; accepted values: http or event or cloudevent | | --source | FUNCTION_SOURCE | The path to the directory of your function. Default: cwd (the current working directory)

| --source | FUNCTION_HANDLER | We're have two options body or path, using env FUNCTION_HANDLER. Default:path )

1. body

using body with json

{
  "action": {"name":"user-update"}
}

--> auto load ./actions/user-update.js
{
  "trigger": {"name":"user-like"}
}

--> auto load ./triggers/user-like.js
2. path: make rest full api
  • /login -> src/login.js
  • actions/user-update -> src/actions/user-update.js
  • triggers/user-buy -> src/actions/user-buy.js

1. Create new node project

yarn init    

2. Install libs

yarn add  easy-functions @google-cloud/functions-framework

3. Make index file. (support ts)

index.js/index.ts

import {handler} from 'easy-functions';

export const easy = handler;

3. Make functions file.

test.js

export default (req, res) => {
    res.send('test ok')
}

4. Run

with npx

npx functions-framework --target=easy

Default endpoint: http://localhost:8080/

Test: http://localhost:8080/test