anchor.diff:      The *CanLoad* guard blocks loading of feature module assets until authorized to do so. If you want to both preload a module and guard
       against unauthorized access, use the [CanActivate](#can-activate-guard) guard instead.
   
  +    **PreloadAllModules**策略不会加载被[CanLoad](#can-load-guard)守卫保护的特征区域，这是因为Angular是这样设计的。
  +    *CanLoad*守卫阻挡加载特征模块资源，直到授权为止。如果你希望预加载一个模块并保护未授权访问，使用[CanActivate](#can-activate-guard)守卫。
  +
   :marked
     We'll update our route configuration to lazy load the *CrisisCenterModule*. We follow the same process as we did when we loaded the *AdminModule* asynchronously.
     In the *crisis-center-routing.module.ts*, we'll change the *crisis-center* path to an *empty path* route.
   
  +  使用与加载异步*AdminModule*一样流程，我们将更新路由配置，来惰性加载*CrisisCenterModule*。
  +  在*crisis-center-routing.module.ts*中，将*crisis-center*的路径修改为*空路径*。
  +
     We'll move our redirect and *crisis-center* route to our `AppRoutingModule` routes and use the `loadChildren` string to load the *CrisisCenterModule*.
     The redirect is also changed to load the `/heroes` route on initial load.
   
  +  接下来，将*redirect*和*crisis-center*路由移动到`AppRoutingModule`路由，并使用`loadChildren`字符串来加载*CrisisCenterModule*。
  +  *redirect*也被修改为初始加载`/heroes`路由。
  +
     Once we're finished, we'll remove the `CrisisCenterModule` from our `AppModule`'s imports.
   
  +  然后将`CrisisCenterModule`移到`AppModule`的`imports`中。
  +
     Here are the updated modules _before enabling preload_:
  +
  +  下面是打开预加载之前的模块修改版：
   
   +makeTabs(
      `router/ts/app/app.module.ts,
  
positive.code: +makeExcerpt('app/app-routing.module.5.ts (can load guard)', 'can-load-guard')
  
  h3#preloading <i>Pre-Loading</i>: background loading of feature areas
  :marked
    We've learned how to load modules on-demand, but we can also take advantage of loading feature areas modules in *advance*. The *Router*
    supports **pre-loading** of asynchronous feature areas prior to navigation to their respective URL. Pre-loading allows us to to load our initial route
    quickly, while other feature modules are loaded in the background. Once we navigate to those areas, they will have already been loaded
    as if they were included in our initial bundle.
  
    Each time a **successful** navigation happens, the *Router* will look through our configuration for lazy loaded feature areas
    and react based on the provided strategy.
  
    The *Router* supports two pre-loading strategies by default:
  
    * No pre-loading at all which is the default. Lazy loaded feature areas are still loaded on demand.
    * Pre-loading of all lazy loaded feature areas.
  
    The *Router* also supports [custom preloading strategies](#custom-preloading) for fine control over which modules to pre-load.
  
    We'll update our *CrisisCenterModule* to be loaded lazily by default and use the `PreloadAllModules` strategy 
    to load _all_ lazy loaded modules as soon as possible.
  
  <a id="preload-canload"></a>
  .l-sub-section
  
negative.code:   Once our application is loaded to our initial route, the *CrisisCenterModule* is loaded eagerly. We can verify this by logging in to the `Admin` feature area and
    noting that the `crisis-center` is listed in the `Preloaded Modules` and logged to the console. We can continue to add feature modules to be selectively loaded eagerly.
  
    一旦应用加载到初始路由，*CrisisCenterModule*被主动加载了。要验证它，登录到`Admin`特征区域，注意`crisis-center`被列到`Preloaded Modules`并输出到控制台。
    我们可以继续添加特征区域，以便有选择的加载它们。
  
  <a id="final-app"></a>
  
  