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

hmr-auto-accept-loader

v1.0.5

Published

Loader that `module.hot.accept` all files that follow a (configurable) naming convention

Downloads

3

Readme

hmr-auto-accept-loader

This javascript loader that adds basic hot module replacement accepts at the end of files, if they import files that end according to the configured naming convention.

if(module.hot) {
  module.hot.accept(['file1.js', 'file2.js', 'etc...'], () => {});
}

When can this be of help? Imagine a Vue/Vuex project that uses webpack-context-hmr or webpack-context-vuex-hmr to get HMR on vuex models, but the models also export their api's like an object:

export const api = {
  getters: {
    getter1: 'module/getters/getter1',
  },
  actions: {
    action1: 'module/actions/action1',
  },
  mutations: {
    mutation1: 'module/mutations/mutation1',
  },
};

// Normal Vuex module setup.....

export default {
    state,
    getters,
    actions,
    mutations,
};

that is used elsewhere to dispatch actions. Then all files using the Vuex modules api must declare the if(module.hot)... with each Vuex module in the array for the HMR to work.

Aint no one got time for that.

A word of caution

Many modules might have parents that need to do some patching for the HMR to work. This loader is not for these kind of modules, but simple ones were the parents would write a empty handler HMR handler () => {} anyways.

if(module.hot) {
  module.hot.accept(['<path-to-module>'], () => {});
}

In the Vuex modules case this works since the exposed object of strings seldom gets updated and the complex part of the module is handled by something like webpack-context-vuex-hmr. There might be a few situations were the HMR might not work because of the empty handlers and thus requires a page refresh. The correct way to avoid this would be to write a proper handler everywhere, but sometimes good enough is good enough. And thats where this loader fits in.

Usage

This loader can for example be used right after eslint in webpacks preloader. Make sure to edit the fileEnding query according to the projects naming convention. Here it looks for files with filenames ending with -store.js.

preLoaders: [
  {
    test: /\.js$/,
    loader: 'hmr-auto-accept-loader?fileEnding=-store.js!eslint',
    include: projectRoot,
    exclude: /node_modules/,
  },
],

License

MIT