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

tamtam-proxy-frontend

v0.3.2

Published

TamTam Proxy Frontend

Downloads

20

Readme

TamTam Proxy Frontend

Folders

  • /html/: Working directory Non build html templates
  • /build/: Folder where html will be build for development
  • /dist/: Folder for distribution (minifying etc)

Grunt

  • grunt: Start with prompts (questions) to help you with the right deployment options
  • grunt server: Build your templates to the build/ folder with a local server with livereload and watchers (this wil be automatically done when you run yo tamtam)
  • grunt dist: Build and minify your project to the dist/ folder for distribution to production server
  • grunt dist:server: Build and minify your project to the dist/ folder for distribution to production server with a local server with livereload and watchers

Adding templates

Edit index.js to export an appropriately named render function for your new template. Then edit the locals object in Gruntfile.js to contain default variables for your new template. The name of the export in index.js and the key used in the locals object should be the same for Grunt to build it properly.

Deploying

  1. Decide what the new SemVer version should be.
  • Increment the "patch" version if you are deploying a tweak or fix (x.x.+1).
  • Increment the "minor" version if you are deploying a new feature (x.+1.0).
  • Increment the "major" version if you are deploying backwards incompatible changes (+1.0.0).
  1. Use git flow release start x.x.x to create a release candidate branch.
  2. Bump the version by editing (or using npm version) and comitting package.json.
  3. Test the release candidate branch with the product owner and commit any bugfixes.
  4. Make sure you've built your assets (grunt dist).
  5. Use git flow release finish x.x.x to merge to master and tag the release.
  6. Use git checkout x.x.x to load the staged version.
  7. Use npm publish to publish this new version to the Node Package Manager.
  8. Use git checkout develop to continue development.