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

library-extend-webpack-plugin

v2.1.0

Published

A webpack plugin that changes the output to an extended library and add it to an existing global library.

Downloads

2

Readme

library-extend-webpack-plugin

A webpack plugin that changes the output to an extended library and add it to an existing global library.

Install

npm i -D library-extend-webpack-plugin

Usage

In your webpack configuration (webpack.config.js):

const LibraryExtendWebpackPlugin = require("library-extend-webpack-plugin");

module.exports = {
    mode: 'production',
    entry: {
        'lib.extend': './src/index.js',
    },
    output: {
        library: 'LIB',
        libraryTarget: 'var',
        filename: '[name].js',
    },
    //...
    plugins: [
        new LibraryExtendWebpackPlugin()
    ]
}

Notice the use of output.library and output.libraryTarget, which indicates a library is being built and the bundle will expose it via a scoped variable named LIB.

NOTE: the value for output.library must as same as the existing global library which you want to add to.

NOTE: the value for output.libraryTarget must be var or umd or jsonp.

Example

Given the above Usage example:

Entry File: index.js

export { default as horn } from './lib/horn';

export { default as bark } from './lib/bark';

Output Bundle

Object.assign(LIB,/******/ (function(modules) {/* webpack bundle code */}));

Function horn and bark are added to global library LIB.

And LIB.horn and LIB.bark work well.

Options

Polyfill

If the browser does not support Object.assign, you can add polyfill as bellow,

new LibraryExtendWebpackPlugin({ polyfill: true })

Exclude

If you want to exclude some files, you can add exclude as bellow,

new LibraryExtendWebpackPlugin({ 
    exclude: function (fileName) {
        return !/\.[tj]s$/i.test(fileName);
    }
})

promptType

Its value can be 'warn' or 'error'. The default value is 'warn'.

'warn': use console.warn.
'error': use console.error and throw an error.

new LibraryExtendWebpackPlugin({ 
    promptType: 'error'
})

debug

Its value should be boolean. The default value is false.

true: It will console log the file as extended library.

new LibraryExtendWebpackPlugin({ 
    debug: true
})

Example of usage on the Browser

For example, the global library file is lib.js, and the output js file we generate with this plugin is lib.extend.js.

NOTE: Only lib.extend.js is generated in this example.

In the browser:

<script src="https://cdn.xx.com/lib.js"></script>
<script src="https://cdn.xx.com/lib.extend.js"></script>

If we use jquery as an example, it will be

<script src="https://code.jquery.com/jquery-1.12.4.js"></script>
<script src="https://code.jquery.com/ui/1.12.1/jquery-ui.js"></script>