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

api-2-love

v2.0.3

Published

The easiest way to create an API to love.

Downloads

8

Readme

api-2-love

The easiest way to create an API to ❤️ — the successor to apilove.

Installing

npm i api-2-love

You may also install ts-node or ts-node-dev to make local development easier.


Getting Started (TypeScript)

First create a file in the root of your project called server.ts, then add the following lines:

import {API2Love} from "api-2-love";

exports.handler = new API2Love().handler;

That's all you need to do to create an API that runs as either a stand-alone server or a serverless Lambda function. API2Love will automatically determine what environment it's running in and set itself up properly to handler API requests.

To run your API service locally all you need to do is run ts-node server.ts, or if you want to get really fancy you can use ts-node-dev --watch ./api,./src --transpile-only server.ts to run your server and automatically restart it when it detects changes.


Building your API Code

Routes

API2Love uses route handling logic similar to Next.js in order to define your API routes. By default, API2Love looks for source files in the ./api directory. The following are some examples of how this works:

./api/admin/index.ts or ./api/admin.ts would be available at https://myapi.com/admin

./api/orders/newest/index.ts or ./api/orders/newest.ts would be available at https://myapi.com/orders/newest

You can also use route parameters like:

./api/orders/[orderID]/index.ts or ./api/orders/[orderID].ts would be available at https://myapi.com/orders/1828972

Code

To write the code to handle your API requests, you simply export a default class. Here is a simple example:

//  From ./api/orders/[orderID]/index.ts
import {Path, Query, Optional} from "api-2-love";

export default class OrderAPI {
    static async getOrderByID(
        @Path // This means the variable named orderID will be pulled from the path of the route
            orderID: string,
        @Query // This means the variable named verbose will be pulled from a query parameter
        @Optional // By default, all variables are required and will return an error if not specified. This denotes that this variable is optional.
            verbose?: boolean
    ) {
        return MyOrderSystem.getOrderByID(orderID, verbose);
    }
}

More documentation coming soon...