Allow configuring towards webpack

[wmertens]

I think that instead of installing the webpack importer plugin manually and setting up the importer resolver (provided that starts working after #142), it would be more in the spirit of XO to simply define webpack: true or webpack: "config-file-name.js".

---

IssueHunt Summary

dflupu has been rewarded.

Backers (Total: $60.00)

• issuehunt ($60.00)

Submitted pull Requests

• #375 add webpack resolver option

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor

[sindresorhus]

Wonder if we can just detect a webpack.config.js file and enable the webpack resolver automagically.

[wmertens]

Not all projects will have one named like that, but indeed it's a nice
start, and then being able to override manually…

On Sun, Oct 23, 2016, 1:34 AM Sindre Sorhus notifications@github.com
wrote:

Wonder if we can just detect a webpack.config.js file and enable the
webpack resolver automagically.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#143 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWlgTfiyVU3AtsB2wyoDItdN3Y8bfKks5q2p10gaJpZM4J8xX9
.

[IssueHuntBot]

@issuehuntfest has funded $60.00 to this issue. See it on IssueHunt

[dflupu]

@sindresorhus

Was looking to submit a PR. Should I add a setting as well, or just make xo detect the config?

[sindresorhus]

Use webpack.config.js if it exists, otherwise the user needs to set a path to the webpack config file using an option called webpack.

[issuehunt-oss]

@sindresorhus has rewarded $54.00 to @dflupu. See it on IssueHunt

• 💰 Total deposit: $60.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $6.00