From opening a bug report to creating a pull request: every contribution is appreciated and welcome. If you're planning to implement a new feature or change the api please create an issue first. This way we can ensure that your precious work is not in vain.
Most of the time, if webpack is not working correctly for you it is a simple configuration issue.
If you are still having difficulty after looking over your configuration carefully, please post a question to StackOverflow with the webpack tag. Questions that include your webpack.config.js, relevant files, and the full error message are more likely to receive responses.
If you have discovered a bug or have a feature suggestion, please create an issue on GitHub.
Do you want to fix an issue? Look at the issues with a tag of X5: work required (PR / Help Wanted). Each issue should be tagged with a difficulty tag -
- D0: My First Commit (Contribution Difficulty)
- D1: Easy (Contribution Difficulty)
- D2: Medium (Contribution Difficulty)
- D3: Hard (Contribution Difficulty)
If you have created your own loader/plugin please include it on the relevant documentation pages:
Setup your local webpack repository
After getting some feedback, push to your fork and submit a pull request. We may suggest some changes or improvements or alternatives, but for small changes your pull request should be accepted quickly.
Some things that will increase the chance that your pull request is accepted:
- Write tests
- Follow the existing coding style
- Write a good commit message
webpack is insanely feature rich and documentation is a huge time sink. We greatly appreciate any time spent fixing typos or clarifying sections in the documentation. See a list of issues with the documentation tag.
Gitter is only for small questions. To discuss a subject in detail, please send a link to your forum or blog in the Gitter chat.