Skip to content

Fix error with filename + npm package. #1886

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 27, 2018
Merged

Fix error with filename + npm package. #1886

merged 3 commits into from
Mar 27, 2018

Conversation

Zicrael
Copy link

@Zicrael Zicrael commented Mar 7, 2018

  1. Webpack as default build to file main.js , not on bundle.js.
  2. Add npm install webpack-cli -D to npm install, If you do not do this console throw next:
    ======================================================
    The CLI moved into a separate package: webpack-cli.
    Please install 'webpack-cli' in addition to webpack itself to use the CLI.
    -> When using npm: npm install webpack-cli -D
    -> When using yarn: yarn add webpack-cli -D
    ======================================================
    So pls fix this, thank`s.

describe your changes...

  • Read and sign the CLA. PRs that haven't signed it won't be accepted.
  • Make sure your PR complies with the writer's guide.
  • Review the diff carefully as sometimes this can reveal issues.
  • Remove these instructions from your PR as they are for your eyes only.

1) Webpack as default build to file main.js , not on bundle.js. 
2) Add npm install webpack-cli -D to npm install, If you do not do this console throw next: 
======================================================
The CLI moved into a separate package: webpack-cli.
Please install 'webpack-cli' in addition to webpack itself to use the CLI.
-> When using npm: npm install webpack-cli -D
-> When using yarn: yarn add webpack-cli -D
======================================================
So pls fix this, thank`s.
@jsf-clabot
Copy link

jsf-clabot commented Mar 7, 2018

CLA assistant check
All committers have signed the CLA.

@montogeek montogeek changed the base branch from master to next March 7, 2018 14:50
@montogeek
Copy link
Member

montogeek commented Mar 7, 2018

npm package change is ok, thanks.
Unfortunately filename is not ok since the guide is using this command: npx webpack src/index.js --output dist/bundle.js which clearly specifies bundle.js as output filename.

Edit: Also moved the base branch to next since it is used to release all new webpack 4 changes

@@ -25,6 +25,7 @@ First let's create a directory, initialize npm, [install webpack locally](/guide
``` bash
mkdir webpack-demo && cd webpack-demo
npm init -y
npm install --save-dev webpack
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line. We already show the installation for webpack and webpack-cli in the next line.

npm install webpack webpack-cli --save-dev

@montogeek montogeek merged commit 2b737d0 into webpack:next Mar 27, 2018
@montogeek
Copy link
Member

Thanks!

montogeek pushed a commit that referenced this pull request Apr 7, 2018
* docs(guides) Fix error with filename + npm package. (#1886)

1) Webpack as default build to file main.js , not on bundle.js. 
2) Add npm install webpack-cli -D to npm install, If you do not do this console throw next: 
======================================================
The CLI moved into a separate package: webpack-cli.
Please install 'webpack-cli' in addition to webpack itself to use the CLI.
-> When using npm: npm install webpack-cli -D
-> When using yarn: yarn add webpack-cli -D
======================================================
So pls fix this, thank`s.

* docs(guides): Added info for v4 and webpack-cli (#1888)

* docs(configuration) Update snippets to comply with webpack v4+ (#1905)

* docs(configuration) Update snippets to comply with webpack v4+

* Expand mode for more info

* fix(docs) Remove git conflict
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants