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

node_modules-path

v2.0.8

Published

Get the path of the `node_modules` folder in your scripts or CLI or package.json

Downloads

11,393

Readme

Get the path of the node_modules folder in your scripts or CLI or package.json. This is useful when you are building a library that can either be used as an npm dependency or directly, see this question on SO.

You can add a parameter in order to look for a specific module. This is useful when npm creates multiple node_modules folder for conflicts reasons.

Installation

$ npm install node_modules-path --save

Test

$ npm test

This project has been battle tested on Silex website builder

Access node_modules in package.json

Use it in your packge.json like this:

"name": "my-super-project",
"scripts": {
  "build": "cp -R `node_modules`/font-awesome/fonts/* dist/fonts/", <=== this will be executed as cp -R /path-to-your-node_modules/or-the-node_modules-of-a-parent/font-awesome/fonts/* dist/fonts/

With a specific module name as a param:

"scripts": {
  "test": "echo  `node_modules` can differ from `node_modules module1`", <=== this will be executed as cp -R /path-to-your-node_modules/or-the-node_modules-of-a-parent/font-awesome/fonts/* dist/fonts/

node_modules folder path from another nodejs script

const node_modules = require('node_modules-path');
console.log('node module path for this project:', node_modules());

This is especially useful to serve fonts in an express app

app.use('/fonts', express.static(Path.resolve(node_modules(), 'font-awesome/fonts/')));
// node_modules() will return the path to your node_modules or to the node_modules of a parent

With a specific module name as a param, which is safer:

app.use('/fonts', express.static(Path.resolve(node_modules('font-awesome'), 'font-awesome/fonts/')));
// node_modules('font-awesome') will return the path to your node_modules or to the node_modules of a parent

node_modules folder path for sass includes

In your package.json script to compile sass:

{
    "build:sass": "sass --load-path `node_modules normalize.css` src/css/app.scss dist/css/app.css"
}