Skip to content

Lazy-Loading route configuration doesn't work with webpack #11372

Closed

Description

@lwensveen

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
Using loadChildren throws TypeError: lang_1.global.System.import is not a function

Expected/desired behavior
Expect it to work without any problems.

Reproduction of the problem
Use webpack and implement loadChildren in routes. I think the problem lies in the point hansl makes in this PR: #11049

Please tell us about your environment:

  • Angular version: 2.0.0-rc.5
  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Chrome 53
  • Language: [all | TypeScript X.X | ES6/7 | ES5]
    Typescript 2.0.0

Activity

  1. vicb commented on Sep 6, 2016

    @vicb
    Contributor

    not actionable

  2. gnujeremie commented on Sep 9, 2016

    @gnujeremie

    What do you mean by "not actionable" ? (Sorry I'm french, I'm not sure to I understand correctly).

    The documentation says :
    Angular provides a built-in module loader that supports SystemJS to load modules asynchronously. If we were using another bundling tool, such as Webpack, we would use the Webpack mechanism for asynchronously loading modules., but there is no information on how to achieve this using webpack and angular.

  3. hunterleaman commented on Sep 9, 2016

    @hunterleaman

    @gnujeremie This discussion may be helpful: PatrickJS/angular-webpack-starter#829

  4. gnujeremie commented on Sep 9, 2016

    @gnujeremie

    @hunterleaman thanks i'll check it out.

  5. angular-automatic-lock-bot commented on Sep 9, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  6. locked and limited conversation to collaborators on Sep 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions