Skip to content

docs(concepts): Simplified the Loaders section #1783

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 4 commits into from
Jan 18, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions src/content/concepts/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,14 +72,15 @@ T> The `output` property has [many more configurable features](/configuration/ou

*Loaders* enable webpack to process more than just JavaScript files (webpack itself only understands JavaScript). They give you the ability to leverage webpack's bundling capabilities for all kinds of files by converting them to valid [modules](/concepts/modules) that webpack can process.

Essentially, webpack loaders transform all types of files into modules that can be included in your application's dependency graph.
Essentially, webpack loaders transform all types of files into modules that can be included in your application's dependency graph (and eventually your bundle).
Copy link
Collaborator

Choose a reason for hiding this comment

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

Would rephrase as and eventually a bundle as users might have multiple.


W> Note that the ability to `import` any type of module, e.g. `.css` files, is a feature specific to webpack and may not be supported by other bundlers or task runners. We feel this extension of the language is warranted as it allows developers to build a more accurate dependency graph.

At a high level, __loaders__ have two purposes in your webpack config. They work to:
At a high level, __loaders__ have two purposes in your webpack configuration:

1. The `test` property identifies which file or files should be transformed.
2. The `use` property says which loader should be used to do the transforming.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Love this change but two minor nitpicks:

  • Can you change says in 2. to indicates?
  • Can you drop the additional blank line (83)? Typically we only include two line breaks before h2 headers.

1. Identify which file or files should be transformed by a certain loader (with the `test` property).
2. Transform those files so that they can be added to your dependency graph (and eventually your bundle). (`use` property)

__webpack.config.js__

Expand Down