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

@jschmold/kor

v0.0.8

Published

`npm i mocha ts-node typedoc typescript --global`

Downloads

2

Readme

Initial Setup

npm i mocha ts-node typedoc typescript --global

Configuration

File: config.yaml

| key | description | values | required? | | ----: | ----------- | ------ | --------- | | mode | Select the mode that the application is to run in. Also affects the database suffix names. (dbsource.development.yaml), default is development | "production", "development" | no | | port | The port that the server will run on. Default 8080 | Any valid port number | no | | dataConfigs | The directory of the database configuration yamls | a directory string | no | | dataSources | The data sources to be loaded into the data connections module. These should align with filenames in the data sources directory | string[] | yes | | verbosity | The level of logging to permit. Default is warn. | debug, log, info, warn, error, none | no | | secret | The API secret key to use for the cookie-parser and csrf protection. | any string | yes |

Modules

Modules are a whole helluva lot like Angular. I built the config this way to enable some sense of familiarity for Angular Developers, and to make it a little easier to manage the whole process of modularizing server applications.

import { ApplicationModule } from '@jschmold/kor';
// import your models here
// import your controllers here

@ApplicationModule(
  models: [
    // models here
  ],
  controllers: [
    // controllers here
  ]
)
export class MyApplicationModule {
  
}