mirror of https://github.com/webpack/webpack.git
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
|
|
||
|
|
# Contributing
|
||
|
|
|
||
|
|
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](http://stackoverflow.com/tags/webpack). Questions
|
||
|
|
that include your webpack.config.js and relevant files are more likely to receive responses.
|
||
|
|
|
||
|
|
**If you have discovered a bug or have a feature suggestion, feel free to create an issue on Github.**
|
||
|
|
|
||
|
|
If you have created your own loader/plugin please incude it on the relevant documentation pages:
|
||
|
|
|
||
|
|
[List of loaders](http://webpack.github.io/docs/list-of-loaders.html)
|
||
|
|
[List of plugins](http://webpack.github.io/docs/list-of-plugins.html)
|
||
|
|
|
||
|
|
### Documentation
|
||
|
|
|
||
|
|
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.
|
||
|
|
|
||
|
|
|
||
|
|
## Submitting Changes
|
||
|
|
|
||
|
|
* Push to your fork and submit a pull request.
|
||
|
|
* Wait for feedback. We may suggest some changes or improvements or alternatives.
|
||
|
|
|
||
|
|
Some things that will increase the chance that your pull request is accepted:
|
||
|
|
|
||
|
|
* Write tests.
|
||
|
|
* Follow our coding style.
|
||
|
|
* Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
|
||
|
|
|