Skip to content

enhanced-resolve as underlying Webpack resolver #345

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

Merged
merged 6 commits into from
Jun 1, 2016
Merged

Conversation

benmosher
Copy link
Member

@benmosher benmosher commented May 17, 2016

In trying to support the end goal of #320, this PR uses the underlying Webpack enhanced-resolve package (and the actual plugins thereof) to resolve under Webpack.

Additional work that would be ideal:

  • reference node-browser-libs, enhanced-resolve via peer dependency with webpack
  • use WebpackOptionsDefaulter from webpack peer to initialize defaults
    • maybe in the future, don't want to figure out how to find webpack from eslint
  • plan support for Webpack 2 (i.e. use ResolverFactory from enhanced-resolve 2.x)
    • should be a sibling package, I think. at least to start

@benmosher benmosher merged commit 05520a3 into master Jun 1, 2016
@benmosher benmosher deleted the enhanced-resolve branch June 3, 2016 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant