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

lokal

v1.1.2

Published

A sane way to handle local imports for npm and node.

Downloads

44

Readme

lokal

A sane way to handle local imports for npm and node.

const myDependency = require('lokal')('myDependency');

Motivation

By default, local imports look like this in Node.js:

const myModule = require('./../../myFolder/myFile.js');

This is unwieldy for a number of reasons:

  • Importing the same file in different places requires a different path.
  • Moving a file requires updating all imports in the file.
  • Moving the file requires updating all files that import it.
  • Other languages/environments have spoiled us.

Install

npm install lokal --save

Usage

Add the following to your package.json file. Note that all of the standard path formats for require() are accepted:

"localDependencies": {
  "dependency1": "test/dependency1/",
  "dependency-2": "/test/dependency2/dependency2.js",
  "dependency3": "test/dependency3/nested/index.js"
}

Import your local dependency like this:

const dependency1 = require('lokal')('dependency1');
const dependency2 = require('lokal')('dependency-2');

A second parameter can be specified as an alternative to require(). For example, to rewire a dependency for writing tests.

const rewire = require('rewire');
const rewiredDependency3 = require('lokal')('dependency3', rewire);

Now when you move a file, the import path only needs to be updated in one place. Additionally, the name used to identify the file as a local dependency in package.json is not tied directly to the file path or file name. It can also be helpful to have a complete list of local dependencies in one location.