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

root-import-utils

v1.1.0

Published

Functions for transforming import/require paths that have a prefix referring to the project root.

Downloads

21

Readme

root-import-utils

Functions for transforming import/require paths that have a prefix referring to the project root.

install

npm install root-import-utils

usage

const {
  hasPrefix,
  stripPrefix,
  getRelativePathToModule,
  getLongRelativePathToModule
} = require('root-import-utils')

API

hasPrefix(prefix, path)

hasPrefix('~', '~/a/b.js') // -> true
  • prefix: string
  • path: string
  • returns: boolean

stripPrefix(prefix, path)

stripPrefix('~', '~/a/b.js') // -> 'a/b.js'
  • prefix: string
  • path: string
  • returns: string the path argument with prefix removed. The / after the prefix is also removed so that the remaining path is relative.

getRelativePathToModule(sourcePathFromRoot, modulePathFromRoot)

getLongRelativePathToModule(sourcePathFromRoot, modulePathFromRoot)

  • sourcePathFromRoot: string relative path from project root to the file that has the import statement or require call
  • modulePathFromRoot: string the module path of import/require with prefix removed so that it is a relative path from project root

getLongRelativePathToModule() simply prepends the relative path from sourcePathFromRoot to the project root to modulePathFromRoot, rather than calculating the most direct path from source to the target module. That means it will return a more verbose path in some situations. See the following example.

getRelativePathToModule(    'a/b/c.js', 'a/b') // -> './'        // directly to module
getLongRelativePathToModule('a/b/c.js', 'a/b') // -> '../../a/b' // back to project root, forward to module