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

v1.1.1

Published

Amok for your webpack

Downloads

4

Readme

webpack-amok-dev-server

Amok for your webpack.

Pros

  • Amok replacing function definitions instead of webpack modules. This means that all references to changed functions in your application will use functions with updated definitions just after they're be replaced. This is very helpful when you're calibrating your function behaviour.

  • WebpackAmokDevServer stores compiled code in memory just like WebpackDevServer. This reduces delay between code change and code replacement.

Cons

  • Amok just replacing your function definitions. So if you want to rerender your compoment or whole app you should subscribe to patch event and implement that behaviour manually.

  • At current moment WebpackAmokDevServer is slower than WebpackDevServer with React Hot Loader on large builds because WebpackAmokDevServer is trying to reload whole build.

  • Amok supports only Google Chrome and Chromium.

Usage

// webpack.config.js

module.exports = {
  // Your webpack configuration...

  amokDevServer: {
    // Same as output.path
    // WebpackAmokDevServer uses this configuration to match file path and url.
    cwd: path.join(__dirname, '.app', 'public'),

    // Same as output.publicPath
    // WebpackAmokDevServer uses this configuration to match file path and url.
    publicPath: '/',

    // Same as output.filename
    // WebpackAmokDevServer uses this configuration to match file path and url.
    filename: 'frontend.js',

    // WebpackAmokDevServer could proxy any request that not matched as webpack build
    // to any other external backend.
    proxy: {
      '*': 'http://localhost:3000',
    },
  },
}
// server.js

var webpack = require('webpack')
var WebpackAmokDevServer = require('webpack-amok-dev-server')

var webpackConfig = require('./webpack.config.js')

var server = new WebpackAmokDevServer(
  webpack(webpackConfig),
  webpackConfig.amokWebServer
)

server.listen(8080, '0.0.0.0', function(error) {
  if (error) {
    console.error(error)
  } else {
    console.log('WebpackAmokDevServer started')
  }
})
node server.js # WebpackAmokDevServer will open Google Chrome on http://localhost:8080