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

html-head-component

v1.2.1

Published

A native web component for everything which might go in the <head> of your document.

Downloads

628

Readme

Travis CI Github Build Codacy Badge Codebeat Badge CodeFactor Badge DeepScan grade Analytics

Head Component

A native web component for everything which might go in the <head> of your document.

Visitor stats

GitHub stars GitHub forks GitHub watchers GitHub followers

Code stats

GitHub code size in bytes GitHub repo size GitHub language count GitHub top language GitHub last commit

Install

npm i html-head-component

# or

yarn add html-head-component

Usage

In your JavaScript/TypeScript entry point:

import 'html-head-component';

You can also include the web component directly from unpkg.com:

import('https://unpkg.com/html-head-component');

or

<script async src="https://unpkg.com/html-head-component"></script>

Then add the component in your HTML/JSX markup:

The custom component should be placed in the <body> tag. If you try to place it in the <head> the browser will explicitly move it in the <body> and you might experience issues with the rest of the elements in the <head>.

Using the data attribute

<html-head-component
	data='
[
	{
		"tag": "title",
		"content": "Title"
	},
	{
		"tag": "meta",
		"name": "author",
		"content": "Scriptex"
	},
	{
		"tag": "link",
		"rel": "stylesheet",
		"href": "./style.css"
	}
]
'
></html-head-component>

Using the src attribute

<html-head-component src="./data.json"></html-head-component>

Usage details

The web component accepts two attributes:

  • src which is a valid path to a JSON file containing array of objects.
  • data which is a valid JSON string which represents an array of objects.

Only one of those attributes should be used. If both are used, the src attribute overwrites the data attribute.

Each object in the JSON array should have a tag property which specifies the HTML element which will be rendered.

The rest of the properties in the object specify the attributes and their content in key:value pairs (attribute:attribute-content).

There are several exceptions:

  1. The document title's content is rendered as innerHTML of the <title> tag.
  2. Each style tag's content property will be rendered as innerHTML of the <style> tag.
  3. Each script tag's content property will be rendered as innerHTML of the <script> tag.
  4. Each noscript tag's content property will be rendered as innerHTML of the <noscript> tag.

React with TypeScript

If you're using React with TypeScript, you need to extends the JSX IntrinsicElements interface so TypeScript knows that the html-head-component element exists.

You can do so in a custom.d.ts file in your project's root folder. Don't forget to add that file in your tsconfig.json!

declare namespace JSX {
	interface IntrinsicElements {
		html-head-component: any;
	}
}

Full example

You can check out the demo usage using data attribute.

Or

You can check out the demo usage using src attribute.

Full list of what can go in the <head> of your document, please check this awesome repository

LICENSE

MIT