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

iwa-cli

v1.1.0

Published

An ImmutableWebApp CLI using oclif and cosmiconfig

Downloads

1,544

Readme

iwa-cli

IWA

An ImmutableWebApp CLI using oclif and cosmiconfig

oclif Version Downloads/week License

Installation

yarn add --dev iwa-cli

npm install --save-dev iwa-cli

Usage

Generate

  1. Create a .iwarc file in the root of your project. The format of this file should look like this.
{
  "env": {
    "all" : {
      "COMMON_ATTRIBUTE": "DEFAULT_VALUE", 
    },
    "production": {
      "KEY": "VALUE_PRODUCTION"
    },
    "development": {
      "KEY": "VALUE_DEVELOPMENT",
      "COMMON_ATTRIBUTE": "DEVELOPMENT_SPESIFIC_VALUE", 
    }
  }
}
  • The all and production environment cannot be omitted!
  • Specify as many environments as you need! In this case we have 2 (one for production and one for development)
  1. Create a script tag with id="iwa" in your index.html or template.index.html
<!DOCTYPE html>
<html lang="en">
  <head></head>
  <body>
    <div id="menu"></div>
    <main id="root"></main>
    <div id="footer"></div>

    <script id="iwa"></script> <!-- This line here is the one -->
  </body>
</html>
  • Make sure you don't have anything it, because it will get erased!
  • Make sure it is placed before all you bundles!
  1. Run the generate command
iwa generate --env=production ./example/index.html  # or the location where the file is located

The command will inject the configuration in the script tag:

<!DOCTYPE html>
<html lang="en">
  <head></head>
  <body>
    <div id="menu"></div>
    <main id="root"></main>
    <div id="footer"></div>
    <script id="iwa">window.env = {"COMMON_ATTRIBUTE": "DEFAULT_VALUE", "KEY":"VALUE_PRODUCTION"}</script>
  </body>
</html>

Override

You can override a variable with process.env variables:

KEY="VALUE_PROCESS" iwa generate ./example/index.html

Remove

You can also erase the configuration from a file, by using the remove command

iwa remove ./example/index.html

Commands

iwa check [INPUT]

Checks HTML file for injected iwa config, useful in a pre-commit hook to prevent commiting injected iwa-config.

USAGE
  $ iwa check [INPUT]

OPTIONS
  -d, --verbose
  -h, --help      show CLI help
  -s, --isStaged  Checks only staged files, and will throw error if config found
  -v, --version   show CLI version

ALIASES
  $ iwa check
  $ iwa c

See code: src/commands/check.ts

iwa generate [INPUT] [OUTPUT]

Generates a HTML file, where window.env configuration is injected

USAGE
  $ iwa generate [INPUT] [OUTPUT]

OPTIONS
  -c, --config=config  Location to look for iwa configuration
  -d, --verbose
  -e, --env=env        [default: production]
  -h, --help           show CLI help
  -v, --version        show CLI version

ALIASES
  $ iwa gen
  $ iwa g

See code: src/commands/generate.ts

iwa remove [INPUT]

Removes injected configuration from an HTML file

USAGE
  $ iwa remove [INPUT]

OPTIONS
  -h, --help     show CLI help
  -v, --version  show CLI version

ALIASES
  $ iwa rm

See code: src/commands/remove.ts