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

frontiera

v0.1.2

Published

A real fast and versatile HTTP proxy.

Downloads

2

Readme

frontiera

Frontiera is a fully asynchronous HTTP Proxy written in Node.JS.

His main purpose is to make proxing tasks as simple and fast as possible. This is achieved by using JSON configuration files inside the config.d directory.

Configuration file

Config files are read and parsed in an alphabetical order. The sections are:

  • domain
  • target
  • log.path
  • log.format
Domain

It's a regular expression! Here basically you should describe you domain(s) so the proxy is able to catch the right requestes.

Target

It's the target server where to proxy the requestes that matched the previous section.

Log.path

It's the path of the log file. It's possible to specify some variables such as {hostname} or {day}, {month}, {year}, etc ...

Log.format

It's the format of every line of the log. It's parsed like the previous section, so you can put variables like {remoteIP}, {userAgent}, {method}, etc ...

Log variables

Here comes some other flexibility. Log.path and log.format are parsed at run time. For example, you can create a log file with these properties:

  • log.path: "/var/log/frontiera/{hostname}.{year}-{month}-{day}.log"
  • log.format: "{isotime} {xforwardedfor} {remoteIP} {method} {path} {statusCode} "{userAgent}" {hostname}"

The available variables are:

  • hostname
  • remoteIP
  • xforwardedfor
  • method
  • path
  • statusCode
  • userAgent
  • year
  • month
  • day
  • hour
  • minute
  • second
  • isotime

Command line options

  • port
  • configdir

Dependencies

Frontiera relies on

TODO

  • Proxying of WS requests
  • Write a better README.md

Known Issues

No known problems (still), but feel free to open issues and don't hesitate to ask for help.

Twitter