Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: support for webpack resolve.alias and resolve.root #31

Closed
acusti opened this issue Mar 1, 2016 · 1 comment
Closed

Comments

@acusti
Copy link

acusti commented Mar 1, 2016

I saw that this was mentioned in #13 (comment) and that it is currently being worked on (:clap:), but thought it might make sense to have it as it’s own issue for other people who have discovered the problem and want to know more about it. But please feel free to close this issue. Also, if there are any parts of the work to support resolve.root / resolve.alias that others could help with, I’d love to contribute!

On to the issue description:


If you set up a webpack alias that you want to be able to use in your imports / requires, those aliases will be interpreted as referring to an external npm package, and this plugin will try to install it. For example, if you define an svg alias to point to a folder of svg files, and then want to require one of those files like require('svg/icon.svg'), you will have npm’s svg package installed into your repo.

@acusti acusti changed the title Feature request: support for webpack resolve.alias Feature request: support for webpack resolve.alias and resolve.root Mar 1, 2016
@ericclemmons
Copy link
Member

This should be resolved in #17! Please re-open if this doesn't work with v3.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants