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

webext-buildtools-builder-types

v1.0.11

Published

Base webext-buildtools builders types definitions

Downloads

16

Readme

Build Status

Introduction

Package with interfaces definitions for all webext-buildtools builders.

If you need complete solution for Web Extension build/deploy, go to webext-buildtools-integrated-builder repo.

Installation

npm install webext-buildtools-builder-types

Purpose

webext-buildtools is a toolkit for building and deploying Web Extensions (browser extensions standard introduced by Google and supported by Chrome, Firefox, Internet Explorer, Opera, etc.).

Use this package to create own builder which implements ISimpleBuilder to make it compatible with other builders in webext-buildtools toolkit.

Main approaches

  1. Builders are classes implemented ISimpleBuilder interface
  2. Each builder represent a particular step of building or deploying webextension
  3. Builder can have options (normally passed to it's constructor) to customize build process

Assets reusing

Different builders can perform similar operations (pack directory to zip for example) or require the same input data (path to extension directory). It's a reason to extract that operations to a separate build step (i.e. another builder). To use common intermediate (or final) build results builders can be chained:

  1. Asset is a wrapping class implemented IBuildAsset which contains some build-related data
  2. Builders can receive data (directly from caller or produced by another builders) needed to perform build (directory path, zip file, manifest file). These data are called inputs
  3. Builders produce assets and optional side effects (like deploy) as a result of their work
  4. Produced assets can be used to pass them on to another builders as inputs
  5. IDisposableBuildAsset is asset which contains data, which can be disposed (removed/cleaned up) after entire build process (temporary files)

Logging

One more defined type is:

type ILogMethod = (level: string, message: string, ...meta: any[]) => any;

It's not used in ISimpleBuilder definition, but usually you can pass logMethod: ILogMethod | undefined to builder constructor to customize logging behaviour.

Example of ILogMethod implementation using winston package:

const winston = require('winston');

const logger = winston.createLogger({
        level: 'info',
        format: winston.format.combine(
            winston.format.splat(),
            winston.format.cli()
        ),
        prettyPrint: JSON.stringify,
        transports: [new winston.transports.Console()]
    });

const logMethod = logger.log.bind(logger);

Using console.log:

const logger = (level, message, ...meta) => {
    console.log(message);
    for (const m of meta) {
        console.log(m);
    }
};