Skip to content
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

Lazyloading module Error 404 when having big project with deep folder structure (Error: (SystemJS) XHR error (404 Not Found) loading http://localhost:3002/src/app/crisis/crisis.module) #12628

Closed
calvinKG opened this issue Oct 31, 2016 · 2 comments

Comments

@calvinKG
Copy link

calvinKG commented Oct 31, 2016

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

I did I POC with Hero's ngmodule tutorial (https://angular.io/docs/ts/latest/guide/ngmodule.html) and found that when you structure your project with sub-folder ( e.g src/app/hero/heroe.module.ts) and implement lazy-loading, you get 404 error point at the module you trying to lazy-load.

Folder Structure
image

Error
image

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

JetBrains Webstorm on windows 7

  • Angular version: 2.0.X

image

  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome

  • Language: [all X| TypeScript X.X | ES6/7 | ES5]

  • Node (for AoT issues): node --version =

@DzmitryShylovich
Copy link
Contributor

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular.

If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants