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

critical-injector

v0.2.1

Published

Injects CSS or JS files contents into HTML file in marked places.

Downloads

1

Readme

Critical Injector

Injects CSS or JS files contents into HTML file in marked places. Actual detection of critical path CSS should be done by other means. On small pages it can me done manually.

You can keep Your code in separate files, process them by other packages (compile, minify) and finally inject their source.

Install

Install with npm

npm install --save critical-injector

Usage

const criticalInjector = require('critical-injector');

var newContent = criticalInjector('src/file.html', {
    basePath: '../htdocs',
});

An example of this in completed form can be seen below:

<html>
<head>
    <!-- injector:css foo bar="baz" -->
    <link rel="stylesheet" href="page-critical-1.css">
    <link rel="stylesheet" href="page-critical-2.css">
    <!-- endinjector -->

    <link rel="preload" href="page-1.css" as="style" onload="this.rel='stylesheet'">
</head>
<body>
    <!-- injector:js defer -->
    <script src="page-critical-1.js"></script>
    <script src="page-critical-2.js"></script>
    <!-- endinjector -->

    <script src="page-1.js" defer></script>
</body>
</html>

The resulting HTML would be:

<html>
<head>
    <style foo bar="baz">/* Merged contents of all CSS files */</style>

    <link rel="preload" href="page-1.css" as="style" onload="this.rel='stylesheet'">
</head>
<body>
    <script defer>/* Merged contents of all JS files */</script>

    <script src="page-1.js" defer></script>
</body>
</html>

API

criticalInjector(src, options)

src

Type: String Default: none

File pathname or HTML content.

Options

options.basePath

Type: String Default: none

Extracted pathnames from [src] or [href] attributes will be appended to basePath.

options.isPath

Type: Boolean Default: true

Specify if first argument is a pathname or HTML content.