forked from webpack/webpack.js.org
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
update master & update translation #380
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make minor fix in the CLI documentation to reflect this comment: webpack#1577 (comment)
Changed example to declare the plugin within `plugins` property.
Rewrite the main sections of the guide to synchronize it with the other core guides. Briefly mention the other utilities that don't require full on examples (details can be found via links). Closes #1258
OpenCollective's structure changed a bit. This address that and makes a few other notable changes: - add additional sponsors - allow to merge additional sponsors to existing sponsors - limit width of logos to 3 x height to disallow very wide logos - format money values with commas
Remove local type def from TypeScript snippet. The @types/node type definition module already declares `__dirname` type: https://git.io/v5Dr9
Add an example to demonstrate using hot module replacement with `webpack-dev-server`'s Node.js API instead of within a normal configuration file.
The article was missing references to `clean-webpack-plugin` in the `webpack.config.js` file and `package.json` files.
As a conclusion, I thought it would be a good idea to show case a high-level explanation of why it's called tree shaking. Once the user reads the guide and ends up with a high-level explanation the word tree shaking will stick to the user's head.
Suggest solutions to the problem right away seems to be a better approach. Use similar text as was used here: https://webpack.js.org/api/module-methods/#import-
Add more information about optimization bailouts. Attempt to transfer content from the blog post to the official docs. I want to follow up with a PR for better bailout reasons. The hope is that the reasons will match those listed in the table.
Clarify interactions between `libraryTarget` and `library`. The interactions between the two and how some of the sections were not well explained, in some cases were incorrect, misleading or missing information.
Add documentation about setting environment variables in CLI with `--env`. Link to webpack _CLI Environment_ section. Add additional usage to `--env` CLI docs.
`pre` loaders run at the beginning, `post` loaders run at the end.
The previous regex was a simpler approach to the lead in content issue in fetched plugin/loader readmes, however it wasn't targeted enough to correctly remove all lead in content. The new approach should be a bit more stable but honestly the real fix here would be so better standardize/enforce the readme template before including these packages in the documentation site. I also think we can simplify the template a bit to make the parsing of these readme easier. Resolves #1600
Update tip based on discussion in #1540.
The changes in #1612 break a significant amount of pre-existing URLs, this commit adds redirects for everything I could see that would be broken.
The padding here is useful for browsers that display a full on scrollbar instead of an overlay scrollbar. We can continue to think about how that space it utilized in future commits/prs.
Modify the doc accordingly to the following tweetstorm where Dan Abramov & Sean Larkin kindly explained this to me. https://twitter.com/TheLarkInn/status/917524723579338752
This change makes inline code blocks wrap so long lines will not be hidden outside paragraph. Resolves #1633
Maintain consistent code from previous guide (development).
Configure TypeScript to compile modules to ES2015 module syntax, enabling webpack to resolve the `import` / `export` syntax on it's own. With this included, the only thing necessary to enable _tree shaking_ is the inclusion of the `UglifyJSPlugin` (which I'm not adding to this article as it is just centered on getting started with TypeScript). Resolves #1627
# Conflicts: # antwar.config.js # src/components/Footer/Footer.jsx # src/components/Navigation/Navigation.jsx # src/components/Site/Site.jsx # src/components/Splash/Splash.jsx # src/content/analyze.md # src/content/api/cli.md # src/content/api/compilation.md # src/content/api/compiler.md # src/content/api/index.md # src/content/api/loaders.md # src/content/api/module-factories.md # src/content/api/plugins.md # src/content/api/plugins/dependency.md # src/content/api/plugins/tapable.md # src/content/api/plugins/template.md # src/content/api/stats.md # src/content/comparison.md # src/content/configuration/dev-server.md # src/content/configuration/module.md # src/content/configuration/stats.md # src/content/contribute/plugin-patterns.md # src/content/contribute/release-process.md # src/content/contribute/writing-a-loader.md # src/content/contribute/writing-a-plugin.md # src/content/development/index.md # src/content/glossary.md # src/content/guides/code-splitting.md # src/content/guides/development.md # src/content/guides/getting-started.md # src/content/guides/production.md # src/content/license.md # src/content/support/index.md # template.ejs
# Conflicts: # src/content/loaders/babel-loader.md # src/content/loaders/bundle-loader.md # src/content/loaders/cache-loader.md # src/content/loaders/coffee-loader.md # src/content/loaders/css-loader.md # src/content/loaders/file-loader.md # src/content/loaders/imports-loader.md # src/content/loaders/istanbul-instrumenter-loader.md # src/content/loaders/json5-loader.md # src/content/loaders/mocha-loader.md # src/content/loaders/node-loader.md # src/content/loaders/raw-loader.md # src/content/loaders/react-proxy-loader.md # src/content/loaders/sass-loader.md # src/content/loaders/script-loader.md # src/content/loaders/source-map-loader.md # src/content/loaders/style-loader.md # src/content/loaders/val-loader.md # src/content/loaders/worker-loader.md # src/content/loaders/yaml-frontmatter-loader.md # src/content/plugins/babel-minify-webpack-plugin.md # src/content/plugins/component-webpack-plugin.md # src/content/plugins/compression-webpack-plugin.md # src/content/plugins/extract-text-webpack-plugin.md
dear-lizhihua
changed the title
update master & update tra
update master & update translation
Oct 15, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
describe your changes...