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

entry-wrap-webpack-plugin

v1.0.0

Published

Wrap entry points with any code

Downloads

8

Readme

EntryWrap webpack plugin

Wrap your bundle entry points

Install

npm i entry-wrap-webpack-plugin -D

Usage example

Example: You're adding a Webpack bundle to an existing project where jQuery is being loaded externally by requireJS. You can tell Webpack to NOT bundle your own version jQuery (as you want to re-use the external version), but then you need to wrap your entry point in a require call to ensure jQuery is loaded before your bundle executes.

That's what this plugin is for.

webpack.config.js

var EntryWrap = require('entry-wrap-webpack-plugin');
var webpack = require('webpack');
module.exports = {
    context: __dirname,
    entry: "./input",
    output: {
        path: __dirname + "/dist",
        filename: "bundle.js"
    },
    externals: {
		"jquery": "jQuery"
	},
    plugins: [
        new EntryWrap('require(["jquery"], function (jQuery) {', '})')
    ]
};

input.js

// jQuery will NOT be included in your bundle
const $ = require('jquery');

... Will result in something along the lines of

require(["jquery"], function (jQuery) {
	// ... webpack bundle here
	// that will not run until jQuery is available on the page
})