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

babel-project-relative-import

v2.0.1

Published

Babel plugin to transform project relative import paths to file relative import paths.

Downloads

6,209

Readme

Babel Project Relative Import

npm build windows build dependencies devDependencies coverage code style

Babel plugin to transform project relative import paths to file relative import paths. Highly inspired by babel-root-import. ~~which works great, but converts to absolute paths, so the built files are not portable accross systems.~~ (This has been changed and it supports relative output paths now, so maybe check it out!)

Tested with babel-cli, babel-loader, grunt-babel and gulp-babel. Does also transform to the same path under Windows.

Notice for Webpack users

If you're using Webpack to bundle your application this plugin may not be needed. You can use Webpacks's resolve.alias for the same behaviour, which also works for require.

Upgrade from 1.x

There are two breaking changes:

  1. Renamed option projectPathSuffix to sourceDir to be less confusing.
  2. The option importPathPrefix automatically added a / to the supplied prefix in previous versions, this has been removed and allows for prefixes like ^dir/test. Just add the / to your importPathPrefix yourself for the old behaviour.

Example

// project/dir/test.js
import Test from '~/otherdir/example.js'

// project/dir/subdir/test.js
import Test from '~/otherdir/subdir/example.js'

Will be transformed to:

// project/dir/test.js
import Test from './../otherdir/example.js'

// project/dir/subdir/test.js
import Test from './../../otherdir/subdir/example.js'

Install

npm install babel-project-relative-import

Usage

Add babel-project-root-import to your plugins in your babel.rc:

{
  "plugins": [
    "babel-project-relative-import"
  ]
}

Plugin Options

sourceDir

If all your source files are inside a subdirectory set this option to the path of the subdirectory so paths get resolved correctly.

{
  "plugins": [
    ["babel-project-relative-import", {
      "sourceDir": "src/"
    }]
  ]
}

importPathPrefix

If you want to have a custom prefix which will be used to detect imports, you can set this option, defaults to ~/.

{
  "plugins": [
    ["babel-project-relative-import", {
      "importPathPrefix": "^"
    }]
  ]
}