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

import-tag

v1.0.1

Published

<h1 align="center">import-tag</h1>

Downloads

1

Readme

Node script that transforms HTML to allows you to use <import src="./path/to/html"> syntax. This allows you to generate static HTML files from separate, smaller components.

Installation

$ npm i import-tag --save

Usage

Usage inside of Node will look something like this at the very least:

const path = require('path');
const importTag = require('import-tag');

(async () => {
  try {
    let compiledHtml = await importTag( path.join(__dirname, './index.html') );
    console.log(compiledHtml);
  } catch(e) {
    console.log(`Error: ${e}`);
  }
})();

Inside of your HTML file, usage looks like this:

<html>
  <body>        
    <h1>Hello World</h1>
    <import src="./test.html">
  </body>
</html>

The import tag does not have a closing tag, and the src attribute must point to a relative path. Nested imports are supported, so in this example test.html can also contain <import src=""> tags, and so on.

Note:

Each import tag src uses the relative directory of the current HTML file. Always use paths relative to the current file!

Example

Given these files:

<!-- index.html -->
<html>
  <body>        
    <h1>Hello World</h1>
    <import src="./components/content.html">
  </body>
</html>
<!-- content.html -->
<p>Welcome to my great site! It's nothing fancy.</p>
<import src="./picture.html">
<!-- picture.html -->
<img src="./path/to/some/pic.jpg" alt="An interesting image">

Assuming this structure:

.
├── components
│   ├── content.html
│   └── picture.html
└── index.html

The output will be:

<!-- index.html -->
<html>
  <body>        
    <h1>Hello World</h1>
    <!-- content.html -->
    <p>Welcome to my great site! It's nothing fancy.</p>
    <!-- picture.html -->
    <img src="./path/to/some/pic.jpg" alt="An interesting image">
  </body>
</html>

Caveats

File paths inside of any other element are not transformed. This means that any paths you use inside of an imported HTML file will be relative to the parent file. Imported HTML files just become one compiled file output, so please take that in to account when writing your JS and CSS as well.