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

@localnerve/web-component-build

v1.5.1

Published

A library to help build web components

Downloads

193

Readme

Web Component Build

Assembles a web component from css, html, and js parts, assists user build flexibility

npm version Verify Coverage Status

Assembles a web component from its parts, allows developers to author the component's parts in separate files.
The parts are processed and written to an output directory, then exposed to a calling build process.

Why This Exists

  1. Author web components in separate JS, CSS, and HTML files
  2. Expose CSS for the web component to builds for computing CSP hashes
  3. Expose HTML for the web component to builds for companion templates and/or DSD for SSR builds
  4. Enable/ease paying these conveniences forward in web component distribution packages

Processing Map

The following is a table of some of the possible input, processing, and output combos. See options for detailed explanations.

| input | processing | output | | ----- | ---------- | ------ | | javascript | minify javascript | javascript | | css | minify css | css | | html | minify html | html | | css, html | minify css, prepend style tag to html, minify html | css, html | | css, html, cssHref | minfy css, prepend style tag to html, prepend link tag to html, minify html | css, html | | cssHref, html | prepend link tag to html, minify html | html | | javascript, css | minify css, merge style tag into javascript, minify javascript | css, javascript | | javascript, css, html | minify css, prepend style tag to html, minify html, merge into javascript, minify javascript | css, html, javascript | | javascript, css, html, cssHref | minify css, prepend style tag to html, prepend link tag to html, minify html, merge into javascript, minify javascript | css, html, javascript | | javascript, html | minify html, merge into javascript, minify javascript | html, javascript | | javascript, html, cssHref | prepend link tag to html, minify html, merge into javascript, minify javascript | html, javascript | | javascript, cssHref | add link tag to javascript, minify javascript | javascript |

By default, html minification minifies any css found therein.

Usage

  // Sample usage, all options specified
  import {build} from '@localnerve/web-component-build';
  const outputDir = 'some/path/output';

  const result = await build(outputDir, {
    cssPath: '/some/path/file.css',
    cssLinkHref: '//some/path/file.css',
    jsPath: '/some/path/file.js',
    htmlPath: '/some/path/file.html',
    jsReplacement: '__REPLACEMENT_IN_JS__',
    terserOptions: { /* terser options */ },
    htmlminOptions: { /* html-minifier options */ },
    cleancssOptions: { /* clean-css options */ },
    minifySkip: false
  });
  // html, js, and css written to `outputDir`
  
  // Retrieve processed content
  const [js, css, html] = await Promise.all([
    result.getJs(), result.getCss(), result.getHtml()
  ]);

  // Retrieve output paths
  const [jsPath, cssPath, htmlPath] = [result.jsPath, result.cssPath, result.htmlPath];

API

This library exports a single function that takes an output directory and processing options, returns a result object.

build (outputDir, options): Result

outputDir {String}, required

Full path to the output directory where css, html, and javascript output are written.

Options {Object}, optional*

* Not really. One or more of cssPath, jsPath, and/or htmlPath must be supplied. They have no default, so if no options are supplied, this library throws an exception.

  • cssPath {String} - Full path to the input css file
    If supplied:

    • css will be minified using cleancssOptions
    • css will be wrapped in a style tag
    • css will be inserted into the javascript file if jsReplacement and jsPath are supplied and no htmlPath supplied
    • css will be prepended to the html file if htmlPath is supplied
  • cssLinkHref {String} - link href to a stylesheet resource to be referenced by the web component
    If supplied:

    • href will be wrapped in a link tag
    • resulting link will be prepended to the html file if htmlPath supplied
    • resulting link will be inserted into the javascript file if no htmlPath supplied and jsReplacement and jsPath supplied
  • htmlPath {String} - Full path to the input html file
    If supplied:

    • css will be prepended in a style tag
    • cssLinkHref will be prepended in a link tag
    • html will be inserted into the javascript file if jsReplacement and jsPath is supplied
  • jsPath {String} - Full path to the input javascript file

  • jsReplacement {String|RegExp} - The replacement pattern for the css or html in the javascript file. See pattern for full documentation
    If supplied:

    • A replacement will be attempted in the javascript file, jsPath must also be supplied
    • If not supplied or falsy, No replacement will be attempted and all assets are just copied to outputDir
  • terserOptions {Object} - The javascript minifier options object
    Defaults:

    {
      ecma: 2022
    }
  • htmlminOptions {Object} - The html minifier options object
    Defaults:

    {
      minifyJS: true,
      minifyCSS: true,
      collapseWhitespace: true,
      removeAttributeQuotes: true,
      removeComments: true
    }
  • cleancssOptions {Object} - The css minifier options object
    Defaults (same as clean-css defaults)

  • minifySkip {Boolean} - True to skip all minifications, defaults to false

Result {Object}

The output of the build process. Allows access to the output paths and full output content. Format:

  • cssPath {String}, The full path to the output css

  • htmlPath {String}, The full path to the output html

  • jsPath {String}, The full path to the output javascript

  • getCss {asyncFunction}, gets the output css

  • getHtml {asyncFunction}, gets the output html

  • getJs {asyncFunction}, gets the output javascript

License