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

@tririga/tri-proxy

v1.0.6

Published

A development HTTP proxy for IBM TRIRIGA UX views.

Downloads

30

Readme

tri-proxy

A simple development HTTP proxy for IBM TRIRIGA UX views.

tri-proxy is a node.js application that serves one or more TRIRIGA UX views from the local file system and proxies all other views files and ajax calls to a TRIRIGA server.

After the tri-proxy is started, it automatically opens the browser. The tri-proxy watch your view files as you work. Changes you make will cause the browser to do a full-page refresh.

Installation

$ npm install @tririga/tri-proxy -g

Synopsis

$ tri-proxy -t <tririga_url>

Options

  • -t, --target url The URL of the TRIRIGA server that the proxy can delegate requests to. It must include the context path.
  • -p, --port port The local TCP port to be used by the proxy server. Defaults to 8001.
  • -v, --views view ... The name of the view(s) to be served from the local file system. Defaults to the current directory name.
  • -d, --dirs directory_path The directory path(s) that contains the files for the view(s) specified by the -v option. Defaults to the current directory path. For Windows, replace the backslashes with forward slashes.
  • -b, --browser browser The browser to open when starting the tri-proxy. Currently available: Chrome, ChromeCanary, Firefox, Opera, Safari , PhantomJS, IE.
  • --version print tri-proxy version.
  • --help print this message.

Usage

To proxy a view called my-app, run the following command:

$ cd my-app/
$ tri-proxy -t <tririga_url>

To proxy multiple views at the same time, run the following command:

$ tri-proxy -t <tririga_url> -v <name_of_view_1> <name_of_view_2> -d <diretory_for_view_1> <diretory_for_view_2>

To proxy using a custom port, run the following command:

$ tri-proxy -t <tririga_url> -p <local_port>