maptalks-rollup-plugin-alias

1.3.4 • Public • Published

maptalks-rollup-plugin-alias

Define aliases when bundling packages with Rollup.

This is a fork of rollup/rollup-plugin-alias

Build Status Dependency Status devDependency Status Coverage Status

Let's take a simple import as an example:

import something from '../../../something';
 
something();

This probably doesn't look too bad on its own. But imagine this is not the only instance in your code base and after a refactor/restructuring this might fall over. With this plugin in place, you can alias ../../../something with something for readability. In case of a refactor only the alias would need to be changed instead of navigating through the code base and changing all imports.

import something from 'something';
 
something();

When we write tests, we may want an easier way to access the local library we are testing or mocking libraries. We may also define aliases to counteract "require hell" and get rid of all those ../../../ imports we may have in the process.

For Webpack users: This is a plugin to mimic the resolve.alias functionality in Rollup.

Installation

$ npm install rollup-plugin-alias

Usage

import { rollup } from 'rollup';
import alias from 'rollup-plugin-alias';
 
rollup({
  entry: './src/index.js',
  plugins: [alias({
    somelibrary: './mylocallibrary'
  })],
});

An optional resolve array with file extensions can be provided. If present local aliases beginning with ./ will be resolved to existing files:

import { rollup } from 'rollup';
import alias from 'rollup-plugin-alias';
 
rollup({
  entry: './src/index.js',
  plugins: [alias({
    resolve: ['.jsx', '.js'],
    foo: './bar'  // Will check for .bar/index.jsx, ./bar.jsx, ./bar/index.js ./bar.js
  })],
});

If not given local aliases will be resolved with a .js extension.

License

MIT, see LICENSE for more information

Package Sidebar

Install

npm i maptalks-rollup-plugin-alias

Weekly Downloads

1

Version

1.3.4

License

MIT

Last publish

Collaborators

  • wsw0108