Update README.md

[chaytanyasinha]

What kind of change does this PR introduce?
fix

currently, the README.md doesn't have important thing that should have been mentioned for webpack as a JavaScript module bundler.

Did you add tests for your changes?
NA

Does this PR introduce a breaking change?
NO,but will help the new user to learn more about webpack.

What needs to be documented once your changes are merged?
Nothing.

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

[webpack-bot]

For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

[webpack-bot]

Hi @chaytanyasinha.

Just a little hint from a friendly bot about the best practice when submitting pull requests:

Don't submit pull request from your own master branch. It's recommended to create a feature branch for the PR.

You don't have to change it for this PR, just make sure to follow this hint the next time you submit a PR.

[webpack-bot]

@chaytanyasinha Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@sokra Please review the new changes.

[chaytanyasinha]

@sokra I have updated the pull request.Please review.

[himanshu010]

CI failed, fix it first

[chaytanyasinha]

@himanshu010 Can you please help me with that,I have tried to do but it's not working.

[himanshu010]

I think you forget to run prettier
run the command: yarn pretty-lint-fix

If prettier is not installed, then install it first using: yarn global add prettier
And then run that command

[chaytanyasinha]

@rishabh3112 Please review

[snitin315]

please reopen your PR for review

[chaytanyasinha]

@snitin315 actually because of CI failure even after running all the commands I closed this and thought of adding another request

[webpack-bot]

@chaytanyasinha The most important CI builds failed. This way your PR can't be merged.

Please take a look at the CI results from travis (failure) and appveyor (success) and fix these issues.

[snitin315]

your branch is too much outdated from upstream (297 commits behind).
First, you need to reset your branch with upstream.

git remote add upstream git@github.com:webpack/webpack.git
git fetch upstream master
git reset --hard upstream/master

then make your changes again, commit and force push the changes.

git push origin master --force

[snitin315]

It looks like you pushed before making new changes and commiting them.

[chaytanyasinha]

@snitin315 yeah by mistake

[snitin315]

now you can push your changes again and open PR.

[chaytanyasinha]

@snitin315 I am trying but
'' 32 problems (32 errors, 0 warnings)
husky > pre-commit hook failed (add --no-verify to bypass)''
this error is comming

[snitin315]

You need to fix those errors first.

[chaytanyasinha]

Is it because of prettier?

[snitin315]

Pre commit hook automatically run prettier/lint for you before each commit. When some errors are not fixable automatically then you have to fix them manually.

[chaytanyasinha]

Okay @snitin315 ,were these problems faced by you too while setting up?

[snitin315]

No