storybookjs / paths.macro

👣 Babel plugin that returns an object containing paths like __dirname and __filename as static values

Babel paths.macro

A babel macro that allows you to "import" the location of the source-file.

The supported paths you can import:

name	example
npmRoot	/Users/you/project
gitRoot	/Users/you/project
wd	/Users/you/project
fileAbsolute	/Users/you/project/src/input.js
file	input.js
extension	.js
filename	input
baseAbsolute	/Users/you/project/src/
base	/src/

The default import is equal to base.

Example

Source file input.js:

import base, { filename } from 'paths.macro';

console.log(base, filename);

alert(filename, base);

function usePathsForSomething() {
  return [filename, base];
}

Output:

console.log("/src/", "input");

alert("input", "/src/");

function usePathsForSomething() {
  return ["input", "/src/"];
}

Config

Install:

yarn add paths.macro

If you don't have babel-macros already you must also install that:

yarn add babel-plugin-macros

Ensure you have babel-plugin-macros in your babel config (.babelrc).

{
  "plugins": ["macros"]
}

paths.macro's Issues

Why is the name "paths.macro" and not "path-macro"?

was looking through https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import

and the examples all have have hyphens instead of "."

Thank you! Just curious to learn more about this.

Install failed

I run 'yarn add babel-plugin-module-paths' command, and then I got this feedback below:

PS C:> yarn add babel-plugin-module-paths
yarn add v1.5.1
[1/5] Validating package.json...
[2/5] Resolving packages...
error An unexpected error occurred: "https://registry.npmjs.org/babel-plugin-module-paths: Not found".
info If you think this is a bug, please open a bug report with the information provided in "C:\GoBear\GoBear_DesignPantry\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Has this module been removed from npm?

Extention should be extension

I only checked the readme, so it might just be the documentation, but there’s a spelling error there.