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

generator-valory

v1.2.2

Published

# Description This yeoman generator will output a boilerplate valory TS project based on a given swagger json file.

Downloads

2

Readme

generator-valory

Description

This yeoman generator will output a boilerplate valory TS project based on a given swagger json file.

Project Structure / Guidelines

├── src                 <─ This folder contains all source code
│   ├── appserver.ts    <─ Main entry point
│   ├── cluster.ts      <─ Starts listener cluster
│   ├── endpoints       <─ This folder contains all endpoints
│   │   └── ... 
│   │── middleware      <─ This folder contains all middleware
│   │   └── ... 
│   └── lib             <─ This folder contains libraries
│       ├── app         <─ This folder is for app specific libraries
│       │   └── ... 
│       ├── config.ts   <─ Reads in config values
│       └── service.ts  <─ Exports app singletons, including config
├── package.json
├── config.json         <─ Stores config structure and defaults
├── tsconfig.json       
└── tslint.json

src/lib/service.ts

This is where you should put all shared instances (and only instances; do not re-export app specific modules) for the app. The type interface for the config also lives here.

src/endpoints

Endpoints should be grouped by common path in files placed in this folder. The endpoint files should export nothing, and should contain nothing but endpoints.

src/middleware

Only middleware class files should be places in this folder. Literal middlewares should not be placed here, but instead be placed as close to where they are used as possible.

src/appserver.ts

This is the main entrypoint. When you add a new endpoint file, you'll have to add it here. Global middleware should also be registered here.

config.json

This files stores your config structure with defaults. The config interface defined in the service file (src/lib/service.ts) should match this file.