Question 1

How do I use regex patterns with aliasify?

Accepted Answer

In the replacements configuration, define regex strings to match aliases, like '_components/(\w+)' mapping to 'src/react/components/$1/index.jsx', allowing dynamic path rewrites across files as per the README.

Question 2

aliasify vs browser field: which should I choose?

Accepted Answer

Use the browser field for speed and simplicity, as it's native to browserify. Choose aliasify for advanced features like regex aliasing, package stubbing, or integrating with other transforms, but expect slower builds.

Question 3

How to stub out a package in aliasify?

Accepted Answer

Set the alias to false in the aliases configuration, e.g., 'd3': false, which replaces require('d3') with an empty object, useful for browser builds as documented in the stubbing section.

Question 4

Can aliasify work with Webpack or other bundlers?

Accepted Answer

No, aliasify is specifically a browserify transform and relies on browserify's API, so it's incompatible with other bundlers without significant adaptation or alternative tools.

Question 5

How to configure aliasify programmatically?

Accepted Answer

Pass a config object directly when calling transform on the browserify instance, e.g., b.transform(aliasify, {aliases: {...}}), allowing dynamic setup without file-based configs.

Question 6

Why isn't aliasify applying to my .coffee files?

Accepted Answer

Check the appliesTo configuration; by default, it targets JS-like extensions. Adjust it to include .coffee or other file types using the browserify-transform-tools options mentioned in the README.

aliasify

What is aliasify?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions