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-lazy-dev-server

v0.0.9

Published

Lazy dev server for webpack

Downloads

607

Readme

Webpack-lazy-dev-server

Webpack server which allow compile entries on demand.

NPM version

npm install webpack-lazy-dev-server
const webpackServer = require('webpack-lazy-dev-server');
const PORT = 4000;
webpackServer.createServer({
  packsDirectory: 'packs', // directory where are you entries for webpack
  host: `http://localhost:${PORT}`, // url which are using for download compiled entries
  config: webpackConfig, // you standart webpack config
  acceptFile: filepath => true, // function for filtering entries in `packsDirectory`
  code: '', // custom code which you can inline for non-compiling entries
  configure: entryList => {} // access to entryList and custom manipuration on it
}).then(app => {
  app.listen(PORT, () => console.log(`Run http://localhost:${PORT}`))
})

All entries will be available according you webpack config

{host}/{publicPath}/{entryname}

in our example it can be

http://localhost:4000/public/entry.js if we have file packs/entry.js and in webpack config you define output.publicPath as public.

Also there is admin panel for precompiled entries. It will be available on http://localhost:4000/admin.

Code examples