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

templateready

v0.2.1

Published

Template on the fly pre-compiler.

Downloads

8

Readme

Template Ready is template on the fly pre-compiler.

templateready --help

Usage:
  templateready [options]

Options:
 -d|--dir <workDirectory>
   The work directory. Use as base path for source directory and output JS
   Default is '.'

 -s|--source <sourceDirectory>
   The source directory with templates.
   If set directory name without path then use work directory as base path: <workDirectory>/templates/
   If set directory name with path then use it as is.
   Default is 'templates'

 -f|--file <outputFile>
   The name of output script file.
   If set file name without path then use work directory as base path: <workDirectory>/templates.js
   If set file name with path then use it as is.
   Pre-comiler will generate common and minified versions of output files.
   Default is 'templates.js'

 -t|--target <targetJsObject>
   The name of object who contain pre-compiled temlates as methods.
   You must ensure that the object already declared in your JS application.
   Default is 'Core.Template'

 -w|--watch
   Watch for changes for source directory.
   When a change template file occurs, rebuild output js files
   No default

 -p|--poll-interval <milliseconds>
   How often to poll watched files for changes.
   Defaults to Node default.

 -h|--help|-?
   Display these usage instructions.

 -q|--quiet
   Suppress DEBUG messages

  Examples:
    templateready myapp.js
    templateready -d ./wwwroot/app -s mytemplates -w -p 1000
    templateready --source ./wwwroot/mytemplates --file ./wwwroot/app/comiled.js --target 'Application.Templates'