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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@hurl/cli

v1.0.5

Published

Create template-generated files with ease from the Command Line

Readme

Table of Contents

Installation

Using npm:

npm install -g @hurl/cli

Using yarn:

yarn global add @hurl/cli

Commands

init

Initialize Hurl

Options

  • --skip: Skip prompts and create default config
    • Type: boolean
    • Default: false
    • Alias: -s
  • --examples: Include example templates when creating config
    • Type: boolean
    • Default: true
    • Alias: -e

Examples

  • Basic (with prompts & examples)

    $ hurl init

    Resulting folder structure:

    project
    │
    └───.hurl
    │   │   .hurl.<js|json|yml|ts>
    │   │
    │   └───templates
    │       │   <language>-example.<js|ts>
    │       │   <language>-example.<js|ts>
    │       │   ...
  • Skip prompts

    $ hurl init -s
    $ hurl init --skip
    $ hurl init --skip=true

    Resulting folder structure:

    project
    │
    └───.hurl
    │   │   .hurl.json
    │   │
    │   └───templates
    │       │   <empty>
  • Don't create example templates

    $ hurl init -e=false
    $ hurl init --examples=false
    $ hurl init --no-examples

    Resulting folder structure:

    project
    │
    └───.hurl
    │   │   .hurl.<js|json|yml|ts>
    │   │
    │   └───templates
    │       │   <empty>

generate

Generate files from a template

Options

  • --paths: The paths to the new files
    • Type: string[]
    • Alias: -p
    • Required
  • --template: The name of the template file/folder
    • Type: string
    • Alias: -t
    • Required
  • --confirm: Should confirm when overriding an existing file
    • Type: boolean
    • Default: true
  • --<some-variable-name>: Value for some template variable
    • Type: string

Examples

  • Create single file with no variables

    $ hurl generate -p example.js -t template.js
  • Create multiple files with no variables

    $ hurl generate -p example.js example2.js -t template.js
  • Create files with variables

    $ hurl generate -p example.js -t example.js --var=value