Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

babel-resolver

Package Overview
Dependencies
Maintainers
1
Versions
19
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

babel-resolver - npm Package Compare versions

Comparing version 0.0.4 to 0.0.6

2

package.json
{
"name": "babel-resolver",
"version": "0.0.4",
"version": "0.0.6",
"description": "Resolve modules from any directory.",

@@ -5,0 +5,0 @@ "main": "lib/createBabelResolver.js",

# Babel Resolver [![NPM version][npm-image]][npm-url] [![Build status][travis-image]][travis-url] [![Coverage status][coveralls-image]][coveralls-url]
Resolve imported modules from any directory.
Resolve modules from any directory.

@@ -25,3 +25,3 @@ ```javascript

require('babel-core/register')({
presets: ['es2015'],
presets: ['es2015'], // required for 'import'
resolveModuleSource: resolver

@@ -44,13 +44,8 @@ });

## Why not just set `NODE_PATH=app`?
## Why not just set NODE_PATH?
Setting `NODE_PATH` is a perfectly valid solution. `babel-node` is for those who:
Setting `NODE_PATH=app` is a perfectly valid solution. `babel-resolver` is for those who:
- find environment variables annoying
- want to resolve modules from more than one directory
```
npm i babel-resolver --save
rm -rf ~/.babel.json
```
## License

@@ -65,2 +60,2 @@

[coveralls-image]: https://coveralls.io/repos/jshanson7/babel-resolver/badge.svg?branch=master&service=github
[coveralls-url]: https://coveralls.io/github/jshanson7/babel-resolver?branch=master
[coveralls-url]: https://coveralls.io/github/jshanson7/babel-resolver?branch=master
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc