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

rollup-plugin-inline-sources

v0.0.3

Published

one rollup plugin to embed static resource into the html file

Downloads

2

Readme

rollup-plugin-inline-sources

A rollup plugin to embed static source into the html file.

Install

npm install rollup-plugin-inline-sources --save-dev

Usage

Create a rollup.config.js configuration file and import the plugin:

import inlineResource from "rollup-plugin-inline-sources";

module.exports = {
  input: "src/index.js",
  output: {
    dir: "output",
    format: "cjs",
  },
  plugins: [inlineResource()],
};

Options

No one is required.

includes

Type: string[] | RegExp Default: /\.(js|css)$/

Specifies extension names of resources that will be inlay into html file.

_Note: If using the RegExp data type, it will compare with the whole resource's name, not only based onto extname.

excludes

Type: RegExp Default: /\.(svg|jpg)$/

excludeAttrs

Type: Array<{ key: string, value: string } | string> Default: ['async', 'defer', { key: 'type', value: 'module' }, { key: 'rel', value: 'modulepreload' }]

Specifies the attributes whick would cause resource being ignored by this plugin's inlay.

base

Type: string Default: ''

Specifies the public path of assets and any other resources.

nonMatched

Type: 2 | 1 | 0 | 'error' | 'warn' | 'none' Default: 2

Specifies the level of error catcher,when it was 2 or error,it will shut down the whole build work. others won't.

cache

Type: boolean Default: true

Turn on this will cache remote 'curl'led download resources for the, it will decrease time spending for next curl download for resource who's name was unchanged.

_Note: It's not support yet

bundleTransform

Type: (bundleName: string, bundleCode: string | undefined) => string Default: () => void 0;

It's a callback function launched in generateBundle lifecycle. you can read bundle's content by the second argument bundleCode, or specifies output with 'return something'. so as concidering, it's dangerous, untill you was quite sure of what you are doing.

_Note: Dangerous usage.

Dynamic Imports

no plan to support it yet. if it is necessary for you please open an issue

LICENSE (MIT)