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

eslint-plugin-object-imports-factory

v0.1.1

Published

ESLint plugin to enforce good practices using object factories to import modules.

Downloads

8

Readme

eslint-plugin-object-imports-factory

ESLint plugin to enforce good practices using object factories to import modules.

Installation

npm install --save-dev eslint-plugin-object-imports-factory

Usage

Add object-imports-factory to the plugins section of your configuration file:

{
  "plugins": ["object-imports-factory"]
}

Then configure the rules you want to use under the rules section.

{
  "rules": {
    "object-imports-factory/require": "error",
    "object-imports-factory/import": "error"
  }
}

Rules

require

This rule enforces the usage of internal functions when using an object factory to import modules with require.

// Good
const factory = {
  foo: function () {
    return require("foo");
  },
  bar: function () {
    return require("bar");
  },
};

// Bad
const factory = {
  foo: require("foo"),
  bar: require("bar"),
};

The usage of internal functions allows to lazy load the modules, which brings massive performance improvements when the modules are not always needed. Without using this pattern, the modules will be loaded at object's creation time.

See https://github.com/tcort/link-check/pull/89/files for an example.

import

This rule enforces the usage of internal functions when using an object factory to import modules with import.

// Good
const factory = {
  foo: () => import("foo"),
  bar: () => import("bar"),
};

// Bad
const factory = {
  foo: import("foo"),
  bar: import("bar"),
};

Although the modules are lazy loaded when using import, they are resolved at the end of the current module's execution, which can be a problem if the modules are not always needed.

To reproduce this problem, consider the following example:

// index.js
const factory = {
  foo: import("foo"),
  bar: import("bar"),
};
console.log(factory);

// foo.js
console.log("foo");

// bar.js
console.log("bar");

When running node index.js, the output will be:

{ foo: Promise { <pending> }, bar: Promise { <pending> } }
foo
bar

But if you enclose them in functions:

// index.js
const factory = {
  foo: () => import("foo"),
  bar: () => import("bar"),
};
console.log(factory);

// foo.js
console.log("foo");

// bar.js
console.log("bar");

The output will be:

{ foo: [Function], bar: [Function] }