NG Upgrade silently fails to bootstrap hybrid application
See original GitHub issueI’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 The upgrade adapter silently fails to bootstrap a hybrid application in the following cases:
- Invalid dependency in angular2 components . See reproduction plunk bellow
- Template errors in angular 2 component. See reproduction plunk bellow
Expected behavior Errors should be reported by the upgrade adapter
Minimal reproduction of the problem with instructions
-
This first plunk illustrates the scenario with an invalid dependency being requested by a component:
https://plnkr.co/edit/am6Ggf61dVG7WLvT7aa3?p=preview
Open the browser’s developer tools when you open the plunk and you should see just a message
bootstrapping ...
To fix the bootstrapping issue, comment lines 21 and 22 in src/app.ts
// COMMENT ME TO FIX BOOTSTRAPPING ISSUE
constructor(foo:bar){
}
-
This second plunk illustrates the scenario with an invalid template being used in an angular 2 component:
https://plnkr.co/edit/pomPcakWVjWLfjVw8qSq?p=preview
Open the browser’s developer tools when you open the plunk and you should see just a message
bootstrapping ...
To fix the bootstrapping issue, comment line 14 in src/app.ts
<!-- COMMENT ME TO FIX BOOTSTRAPPING ERROR -->
<BAD TEMPLATE div></div>
What is the motivation / use case for changing the behavior?
Improve development experience
Please tell us about your environment:
-
Angular version: 2.0.1
-
Browser: all
-
Language: TypeScript 2.0.3
-
Node (for AoT issues):
node --version
= N/A
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:14 (6 by maintainers)
+1
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.