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

@kpdecker/linoleum-webpack

v3.2.1

Published

Webpack build infrastructure for Linoleum projects

Downloads

23

Readme

Linoleum-Webpack

Webpack build infrastructure for Linoleum projects.

Usage

Within Gulpfile.js:

// Init global state
var Linoleum = require('@kpdecker/linoleum');

// Include optional linoleum tasks
var LinoleumWebpack = require('@kpdecker/linoleum-webpack');

Global APIs:

  • CLIENT_ENTRY: Path to the client build entry point
  • KARMA_TEST_FILES: Glob representing karma test files. May be overridden. Will be ignored from mocha tests.
  • SERVER_PORT: Port that the webpack dev server instance will proxy.
  • DEV_SERVER_PORT: Port that the webpack dev server will be hosted on.

(Added to the Linoleum root project)

Defines:

  • webpack task which generates webpack build packages. This includes:

    • lib/$client$/: Web client package
    • lib/index.js: Node server package
    • lib/$cover$/: Test coverage node package

    This is intended to replace the babel build tasks for projects using Webpack, not augment them.

  • webpack:dev-server task which launches a webpack developer server instance

  • watch:karma task which runs Karma tests in watch mode.

  • cover:server task which runs webpack coverage tests in node.

  • cover:web task which runs webpack coverage tests in browser.

For webpack tests, each package will filter the tests that are imported based on the file suffix. .server.js tests will only run under the cover:server task and .web.js tests will only run under the cover:web task. Simple .js files will run under both.

When running in watch mode, the optional LinoleumWebpack.watchHandler change handler can be used to ensure that rebuilds always invalidate. Depending on the exact OS, Editor, and Node versions in use, the default configuration might not always trigger.

Linoleum.watch(WATCH_FILES, 'build', {
  onChange: LinoleumWebpack.watchHandler
});

Common issues

Karma

Travis needs to be configured to use Firefox when running Karma tests. This can be done with the following config:

before_script:
  - export DISPLAY=:99.0
  - sh -e /etc/init.d/xvfb start
  - sleep 3 # give xvfb some time to start

If a Error: Path doesn't exist '/_karma_webpack_/karma-test.js' or similar is seen when running Karma, this is due to the Karma tests directory not existing.