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

native-require

v1.1.4

Published

To resolve external modules for bundlers

Downloads

6,502

Readme

native-require

Resolve requires in an easy way

npm Travis Codecov branch license

JavaScript Style Guide

Getting started

Install
$ npm install native-require --save
Require or Resolve from where you want
import _require from 'native-require'

// Seems normal but useful to resolve external modules when using bunlders
const axios = _require('axios')

// Require from specific directory
const model = _require.from('./src/model')

const User = model('./user')
// Alias
const User = model.require('./user')

Features

  • Simple to use, no more you didn't need
  • Relative requires from specific directory
  • Resolve external warnings from bundlers (Webpack, Rollup, etc.)
  • Higher performance (no Module will be created)
  • No dependencies
  • Compatible in Node v4, v6 and v8

API

_require(request) (default export)

Same as require(), but resolve external problems from bundlers

.require(request)

Alias of _require()

.resolve(request)

Same as require.resolve()

.from(basedir)

Create a new native-require instance but lookup modules from basedir

One basedir only create instance once, so never worry about used like

_require.from(modelDir).require('./user')
_require.from(modelDir).require('./post')
_require.from(modelDir).require('./comment')