Before you submit an issue, please search the issue tracker,maybean issue for your problem alreadyexists and the discussion might inform you of workarounds readily available.

Before you submit an issue, please search the issue tracker, an issue for your problemmayalreadyexist, and the discussion might inform you of workarounds readily available.

We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we ask that youtoprovide a minimal reproduction scenario (github repo or failing test case). Having a live, reproducible scenario gives us a wealth of important information without going back & forth to you with additional questions like:

We want to fix all the issues as soon as possible, but before fixing a bug, we need to reproduce and confirm it. In order to reproduce bugs, we ask that you provide a minimal reproduction scenario (GitHub repo or failing test case). Having a live, reproducible scenario gives us a wealth of important information without going back & forth to you with additional questions like:

- version of Webpack used

- version of the loader / plugin you are creating a bug report for

- the use-case that fails

A minimal reproduce scenario allows us to quickly confirm a bug (or point out config problems) as well as confirm that we are fixing the right problem.

We will be insisting on a minimalreproduce scenario in order to save maintainers time and ultimately be able to fix more bugs. We understand that sometimes it might be hard to extractessentials bits of code from a largercode-base but we really need to isolate the problem before we can fix it.

We will be insisting on a minimalreproduction scenario in order to savethemaintainers' time and ultimately be able to fix more bugs. We understand that sometimes it might be hard to extractessential bits of code from a largercodebase, but we really need to isolate the problem before we can fix it.

Unfortunately, we arenot ableto investigate/ fix bugs without a minimal reproduction, so if we don't hear back from you weare going to close an issue that doesn't have enough info to be reproduced.

Unfortunately, we areunableto investigateor fix bugs without a minimal reproduction, so if we don't hear back from you, wemay have to close an issue that doesn't have enough info to be reproduced.

You can_request_ a new feature by creating an issue onGithub.

You can_request_ a new feature by creating an issue onGitHub.

If you would like to_implement_ a new feature, please submit an issue with a proposalfor your work`first`,tobe sure that particular makes sense for the project.

If you would like to_implement_ a new feature yourself, please**firstsubmit an issue** with a proposal toensure the idea aligns with the goals of the project.

Before you submit your Pull Request (PR) consider the following guidelines:

- SearchGithub for an open or closed PRthat relatesto your submission. You don't wanttoduplicate effort.

- Commit your changes using a descriptive commit message that follows our[commit message conventions](#commit).Adherence to these conventionsisnecessary because release notes are automatically generated from these messages.

-Fill out our`Pull Request Template`.Your pull requestwill not beconsidered if it is ignored.

- Please sign the`Contributor License Agreement (CLA)` whena pull request is opened. We cannot accept yourpull requestwithoutthis. Make sureyou signwith the primary email address associated with your local/ github account.

- SearchGitHub for an open or closed PRrelatedto your submissiontoavoid duplicating effort.

- Commit your changes using a descriptive commit message that follows our[commit message conventions](#commit).Thisisimportant because release notes are automatically generated from these messages.

-Complete the`Pull Request Template`.Pull requests that ignore the templatewill not bereviewed.

- Please sign the`Contributor License Agreement (CLA)` whenyou open your pull request. We cannot accept yourcontributionwithoutit. Be sureto signusing the primary email address associated with your localand GitHub account.

The**header** is mandatory and the**scope** of the header is optional.

Any line of the commit message cannot be longer 100 characters! This allows the message to be easier

to read on GitHub as well as in various git tools.

No line in the commit message should exceed 100 characters! This makes the message easier to read on GitHub as well as in various Git tools.

The footer should contain a[closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.

Must be one of the following:

Must be one of the following commit types:

-**build**: Changes that affect the build system or external dependencies (example scopes: babel, npm)

-**chore**: Changes that fall outside of build / docs that do not effect source code (example scopes: package, defaults)

The scope is subjective & depends on the`type` see above. A good example would be a change to a particular class/ module.

The scope is subjective & depends on the`type` see above. A good exampleof a scopewould be a change to a particular classor module.

The subject contains a succinct description of the change:

- use the imperative, present tense: "change" not "changed"nor "changes"

- use the imperative, present tense: "change" not "changed"or "changes"

- don't capitalize the first letter

- no dot (.) at the end

Just as in the**subject**, use the imperative, present tense: "change" not "changed"nor "changes".

The body should include the motivation for the change and contrastthis with previous behavior.

Just as in the**subject**, use the imperative, present tense: "change" not "changed"or "changes".

The body should include the motivation for the change and contrastit with previous behavior.

The footer should contain any information about**Breaking Changes** and is also the place to

reference GitHub issues that this commit**Closes**.

The footer should include any information about**Breaking Changes** and is also the place to reference GitHub issues that this commit**Closes**.

**Breaking Changes**should start with the word`BREAKING CHANGE:`witha space or twonewlines. The rest of thecommit message is then used for this.

**Breaking Changes**must start with the word`BREAKING CHANGE:`followed bya space or twonew lines. The rest of thebreaking change details should be provided after this.

Example

You may have the need to test your changes in a real-world project or dependent

module. Thankfully, Github provides a means to do this. Add a dependency to the

`package.json` for such a project as follows:

You may need to test your changes in a real-world project or a dependent module. Thankfully, GitHub provides a means to do this. To add a dependency to the`package.json` of such a project, use the following syntax:

{

When submitting your contribution, a CLA (Contributor License Agreement) bot willcome by toverifythat you signed the[CLA](https://easycla.lfx.linuxfoundation.org/#/?version=2).

When submitting your contribution, a CLA (Contributor License Agreement) bot will verifywhether you have signed the[CLA](https://easycla.lfx.linuxfoundation.org/#/?version=2).

If it is your first time, it will link you to the right place to sign it.

However, ifyou have committedyourcontributions using an email that is notthesame as youremailused onGitHub, the CLA botcan't accept your contribution.

However, ifthe email used inyourcommits doesn’t matchthe emailassociated with yourGitHub account, the CLA botwon’t accept your contribution.

Run`git config user.email` to see your Git email, and verify it with[your GitHub email](https://github.com/settings/emails).

Run`Git config user.email` to see your Git email, and verify it with[your GitHub email](https://github.com/settings/emails).