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

htmlify-js

v1.0.5

Published

Simple tool for maintaining files in a static website.

Downloads

27

Readme

htmlify-js

A simple library to manage files in a static website where reusability and component functionality is needed.

  • ✅ Compile files to html using reusable compoenents.
  • ✅ Nest compoenents within components
  • ✅ Need to make a change? Update a component, recompile, and all files using it will update.
  • ✅ Watch option for live development

Installation

Global installation

npm install htmlify-js -g

Local installation

npm install htmlify-js --save-dev

Usage

Create an index.comp file

@include "header"

  <h1>Htmlify makes static code resuable!</h1>

@include "footer"

In the same directory, create _header.comp and _footer.comp files (_ is used to identify sub-components).

_header.comp

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>htmlify-js</title>
</head>
<body>

_footer.comp

</body>
</html>

Now to compile, run:

npx htmlify-js

index.html (output)

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Document</title>
</head>
<body>

  <h1>Htmlify makes static code resuable!</h1>

</body>
</html>

Environment variables

Warning ⚠️: Do not environment variables that contain sensitive info. The variables will end up in the compiled HTML and anyone is able to view them. Only include variables that are meant to be seen, such as public keys etc..

Used as follows:

.env

MY_EXAMPLE_ENV_VAR="Welcome!"

index.comp

<div>@env "MY_EXAMPLE_ENV_VAR"</div>

index.html (output)

<div>Welcome!</div>

Configuration

For more control, create an htmlify.config.json file in the root directory of where you run the compilation:

htmlify.config.json (default settings)

{
  "targetDir": ".",
  "outDir": ".",
  "watch": false,
  "inputExtension": "comp",
  "outputExtension": "html",
  "outputExtension": false
}

Settings

  • targetDir directory where the source files are located
  • outDir directory where the compiled files will be at
  • inputExtension extension of files that htmlify-js will look for to compile (.comp by default)
  • outputExtension extension of files that htmlify-js will compile to (.html by default)
  • envDir directory of .env file to use environtment variables in template (false by default)