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-plugin-relative-path-import

v2.0.1

Published

Babel Plugin to enable relative root-import

Downloads

1,512

Readme

babel-plugin-relative-path-import

Babel plugin to add the opportunity to use import and require with root based paths. Build Status Build Status https://github.com/dayitv89/babel-plugin-relative-path-import

Versions:

  • Babel 7 supports : v2.0.1
  • Previous stable version: v1.0.5

Example

// Usually
import UserAction from '../../../actions/UserAction';
const Colors = require('../../theme/Colors');

// With babel-plugin-relative-path-import
import UserAction from '@actions/UserAction';
const Colors = require('@theme/Colors');

Install

npm

npm install babel-plugin-relative-path-import --save-dev

yarn

yarn add babel-plugin-relative-path-import --dev

Use

Add a .babelrc file and write:

{
  "plugins": [
		[
			"babel-plugin-relative-path-import",
			{
				"paths": [{
					"rootPathPrefix": "~", // `@` is the default so you can remove this if you want
					"rootPathSuffix": "src/js"
				},
				{
					"rootPathPrefix": "@",
					"rootPathSuffix": "other-src/js"
				},
				{
					"rootPathPrefix": "@parent",
					"rootPathSuffix": "../../src/in/parent" // since we support relative paths you can also go into a parent directory
				},
				{
					"rootPathPrefix": "@some",
					"rootPathSuffix": "../../src/in/some" // since we support relative paths you can also go into a parent directory
				}]
			}
		]
	]
}

// Now you can use the plugin like:
import foo from '~/my-file';
const bar = require('@/my-file');

// Usually
import ParentExample from '../../src/in/parent/example.js';
const OtherExample = require('../../src/in/some/example.js');

// With Babel-Root-Importer
import ParentExample from '@parent/example.js';
const OtherExample = require('@some/example.js');

or pass the plugin with the plugins-flag on CLI

babel-node myfile.js --plugins babel-plugin-relative-path-import

Don't let ESLint be confused

If you use eslint-plugin-import to validate imports it may be necessary to instruct ESLint to parse root imports. You can use eslint-import-resolver-babel-plugin-root-import

    "import/resolver": {
      "babel-plugin-relative-path-import": {}
    }

Don't let Flow be confused

If you use Facebook's Flow for type-checking it is necessary to instruct it on how to map your chosen prefix to the root directory. Add the following to your .flowconfig file, replacing {rootPathPrefix} with your chosen prefix and {rootPathSuffix} with your chosen suffix.

[options]
module.name_mapper='^{rootPathPrefix}/\(.*\)$' -> '<PROJECT_ROOT>/{rootPathSuffix}/\1'

FYI

Webpack delivers a similar feature, if you just want to prevent end-less import strings you can also define aliases in the resolve module, at the moment it doesn't support custom/different symbols and multiple/custom suffixes. READ MORE

Want to revert back to relative paths?

Sometimes tooling might not be up to scratch, meaning you lose features such as navigation in your IDE. In such cases you might want to revert back to using relative paths again. If you have a significant amount of files, it might be worth looking into tooling to help you with the conversion.

Distributing package?

While distributing package somewhere, .babelrc file has problem to resolve the path. To fix that you should run postinstall inside your package.json.

// BabelPostScript.js
(function() {
	const path = process.cwd();
	if (path.includes('node_modules')) {
		const dataPrefix = path.substring(path.indexOf('node_modules')) + '/';
		const fs = require('fs');
		const config = {
			fileName: './.babelrc',
			fileType: 'utf8',
			dataPrefix
		};

		fs.readFile(config.fileName, config.fileType, function(err, data) {
			const bableDefault = JSON.parse(data);
			bableDefault.plugins[0][1].paths.forEach(i => {
				i.rootPathSuffix = `${config.dataPrefix}${i.rootPathSuffix}`;
			});
			fs.writeFile(config.fileName, JSON.stringify(bableDefault, null, 2), function(err) {
				if (err) throw err;
				console.log('BabelPostScript for babel-plugin-relative-path-import run: complete');
			});
		});
	}
})();

Run this script using postinstall inside package.json

{
	...
	"scripts": {
		...
		"postinstall": "node ./BabelPostScript.js"
	},
	...
}

Credit

Improved by Gaurav D. Sharma, inspired & originally taken from entwicklerstube