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

webpack-config-wapplr

v1.0.20

Published

The default Webpack config for Wapplr structure

Downloads

29

Readme

Webpack-config-wapplr

This package includes Webpack configuration used by Wapplr.

Module resolver

"Sibling packages" mean that the package name can be found in the parent directory. There is a package.json and a wapplr.json file. Eg: import myPackage from 'my-package'. If there is ../mypackage folder and there are package files they will work with alias.

  • It the import use a file from dist folder import mySubPackage from 'mypackage/dist/myfile the path will replace to mypackage/src/myfile. The "dist" and "src" folders read from mypackage\wapplr.json file {"paths": {srcPath: "...", distPath: "...""}} that is configurable.

  • In the next step redirect the sibling packages to ../packageName/src/client or ../packageName/src/server, it depends on bundle target.

  • At the end it will change _css.js to .css if the css file is exists. TODO: It should be outsource babel-plugin-css-to-js-transform...

Style loading

Css files import with css-loader and the styleLoader add _getCss function and module object to exports object.

  • If the css is from a Sibling package folder or from the Package folder it will load with styleLoader.
  • The other css will load with just css-loader.
/*styleLoader.js*/

const loaderUtils = require("loader-utils");

function styleLoader() {

    function loader() {}

    loader.pitch = function pitch(request) {

        if (this.cacheable) {
            this.cacheable()
        }

        return `
    var css = require(${loaderUtils.stringifyRequest(this, `!!${request}`)});
    exports = module.exports = css.locals || {};
    exports._getCss = function() { return "" + css; };
    exports._module = module;
`
};

    return loader;

}

module.exports = styleLoader();