Merge branch 'master' into split-chunks-plugin-article

jeremenichelli · web-flow · commit c4b21c10a572 · 2018-04-03T11:16:16.000+02:00
diff --git a/src/content/api/plugins.md b/src/content/api/plugins.md
@@ -10,7 +10,7 @@ contributors:
 
 Plugins are a key piece of the webpack ecosystem and provide the community with
 a powerful way to tap into webpack's compilation process. A plugin is able to
-[hook](/api/compiler/#event-hooks) into key events that are fired throughout each compilation. Every step
+[hook](/api/compiler-hooks/#hooks) into key events that are fired throughout each compilation. Every step
 of the way, the plugin will have full access to the `compiler` and, when
 applicable, the current `compilation`.
 
@@ -41,7 +41,7 @@ noted.
 Depending on the hooks used and `tap` methods applied, plugins can function in
 a different number of ways. The way this works is closely related to the
 [hooks](https://github.com/webpack/tapable#tapable) provided by `Tapable`. The
-[compiler hooks](/api/compiler/#event-hooks) each note the underlying `Tapable` hook indicating which
+[compiler hooks](/api/compiler-hooks/#hooks) each note the underlying `Tapable` hook indicating which
 `tap` methods are available.
 
 So depending which event you `tap` into, the plugin may run differently. For
@@ -96,5 +96,5 @@ different hook classes and how they work.
 
 ## Next Steps
 
-See the [compiler hooks](/api/compiler/#event-hooks) section for a detailed listing of all the available
+See the [compiler hooks](https://webpack.js.org/api/compiler-hooks/) section for a detailed listing of all the available
 `compiler` hooks and the parameters they make available.
diff --git a/src/content/api/resolvers.md b/src/content/api/resolvers.md
@@ -7,7 +7,7 @@ sort: 3
 Resolvers are created using the `enhanced-resolve` package. The `Resolver`
 class extends the `tapable` class and uses `tapable` to provide a few hooks.
 The `enhanced-resolve` package can be used directly to create new resolvers,
-however any [`compiler` instance](/api/compiler/) has a few resolver instances that can be
+however any [`compiler` instance](/api/node/#compiler-instance) has a few resolver instances that can be
 tapped into.
 
 Before reading on, make sure you at least skim through the
@@ -50,8 +50,7 @@ with the [`resolve`](/configuration/resolve/) or [`resolveLoader`](/configuratio
 users to change the resolving behavior through a variety of options including
 through resolve `plugins`.
 
-The resolver plugins, e.g. [`DirectoryNamedPlugin`]
-(https://github.com/shaketbaby/directory-named-webpack-plugin), can be included
+The resolver plugins, e.g. [`DirectoryNamedPlugin`](https://github.com/shaketbaby/directory-named-webpack-plugin), can be included
 directly in `resolve.plugins` rather than using standard plugins. Note that the
 `resolve` configuration affects the `normal` and `context` resolvers while
 `resolveLoader` is used to modify the `loader` resolver.
diff --git a/src/content/configuration/resolve.md b/src/content/configuration/resolve.md
@@ -207,7 +207,7 @@ Tell webpack what directories should be searched when resolving modules.
 
 Absolute and relative paths can both be used, but be aware that they will behave a bit differently.
 
-A relative path will be scanned similarly to how Node scans for `node_modules`, by looking through the current directory as well as it's ancestors (i.e. `./node_modules`, `../node_modules`, and on).
+A relative path will be scanned similarly to how Node scans for `node_modules`, by looking through the current directory as well as its ancestors (i.e. `./node_modules`, `../node_modules`, and on).
 
 With an absolute path, it will only search in the given directory.
 
diff --git a/src/content/contribute/writing-a-plugin.md b/src/content/contribute/writing-a-plugin.md
@@ -13,7 +13,7 @@ A plugin for `webpack` consists of
 
 - A named JavaScript function.
 - Defines `apply` method in it's prototype.
-- Specifies an [event hook](/api/compiler/#event-hooks) on which to bind itself.
+- Specifies an [event hook](/api/compiler-hooks/) on which to bind itself.
 - Manipulates webpack internal instance specific data.
 - Invokes webpack provided callback after functionality is complete.
 
diff --git a/src/content/guides/getting-started.md b/src/content/guides/getting-started.md
@@ -167,7 +167,7 @@ __dist/index.html__
    </head>
    <body>
 -    <script src="./src/index.js"></script>
-+    <script src="dist/bundle.js"></script>
++    <script src="bundle.js"></script>
    </body>
   </html>
 ```
diff --git a/src/scripts/fetch_package_names.js b/src/scripts/fetch_package_names.js
@@ -35,6 +35,13 @@ function main() {
 function fetchPackageNames(options, cb) {
   const github = new GitHubApi();
 
+  if(process.env.GITHUB_TOKEN) {
+    github.authenticate({
+      type: 'token',
+      token: process.env.GITHUB_TOKEN
+    });
+  }
+
   // XXX: weak since this handles only one page
   github.repos.getForOrg({
     org: options.organization,
diff --git a/yarn.lock b/yarn.lock
@@ -7439,9 +7439,9 @@ tap-parser@^6.0.1:
     js-yaml "^3.2.7"
     minipass "^2.2.0"
 
-"tap-render@github:munter/tap-render#0.1.7-patch1":
+tap-render@Munter/tap-render#0.1.7-patch1:
   version "0.1.7"
-  resolved "https://codeload.github.com/munter/tap-render/tar.gz/35bf3ac21c4fd2776d8569d5e8a1ab62df1f6d4f"
+  resolved "https://codeload.github.com/Munter/tap-render/tar.gz/35bf3ac21c4fd2776d8569d5e8a1ab62df1f6d4f"
   dependencies:
     jsonify "0.0.0"
     pause-stream "0.0.7"
