Angular 6 upgrade run time issue for optimized build
up vote
0
down vote
favorite
I have upgraded my current project from angular 4 to version 6. I followed the steps mentioned in this URL: https://update.angular.io/
I corrected the import definitions for RxJs classes and operators according to version 6+, used pipe operators to combine multiple operators and resolved the name of operators that were changed in RxJs version 6.
I am not facing any issue when compiling the build for development but observing issue while running the application with optimized build **ng --prod**.
Here is my current package.json file.
"dependencies": {
...
"primeng": "4.0.3",
"rxjs": "^6.3.2",
"rxjs-compat": "^6.3.2",
"tixif-ngx-busy": "0.0.8",
"zone.js": "^0.8.26"
}
and here is the error in console.
https://i.stack.imgur.com/RY565.png
migration angular6 rxjs6
asked Nov 11 at 11:08
Milind Kali
11
add a comment |
up vote
0
down vote
favorite
I have upgraded my current project from angular 4 to version 6. I followed the steps mentioned in this URL: https://update.angular.io/
I corrected the import definitions for RxJs classes and operators according to version 6+, used pipe operators to combine multiple operators and resolved the name of operators that were changed in RxJs version 6.
I am not facing any issue when compiling the build for development but observing issue while running the application with optimized build **ng --prod**.
Here is my current package.json file.
"dependencies": {
...
"primeng": "4.0.3",
"rxjs": "^6.3.2",
"rxjs-compat": "^6.3.2",
"tixif-ngx-busy": "0.0.8",
"zone.js": "^0.8.26"
}
and here is the error in console.
https://i.stack.imgur.com/RY565.png
migration angular6 rxjs6
asked Nov 11 at 11:08
Milind Kali
11
don't share code (including stack traces) as images. your exception is not visible / readable in attached screenshot. Instead copy paste your error to the question as text in readable fashion.
– muradm
Nov 11 at 20:41
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have upgraded my current project from angular 4 to version 6. I followed the steps mentioned in this URL: https://update.angular.io/
I corrected the import definitions for RxJs classes and operators according to version 6+, used pipe operators to combine multiple operators and resolved the name of operators that were changed in RxJs version 6.
I am not facing any issue when compiling the build for development but observing issue while running the application with optimized build **ng --prod**.
Here is my current package.json file.
"dependencies": {
...
"primeng": "4.0.3",
"rxjs": "^6.3.2",
"rxjs-compat": "^6.3.2",
"tixif-ngx-busy": "0.0.8",
"zone.js": "^0.8.26"
}
and here is the error in console.
https://i.stack.imgur.com/RY565.png
migration angular6 rxjs6
asked Nov 11 at 11:08
Milind Kali
11
I have upgraded my current project from angular 4 to version 6. I followed the steps mentioned in this URL: https://update.angular.io/
I corrected the import definitions for RxJs classes and operators according to version 6+, used pipe operators to combine multiple operators and resolved the name of operators that were changed in RxJs version 6.
I am not facing any issue when compiling the build for development but observing issue while running the application with optimized build **ng --prod**.
Here is my current package.json file.
"dependencies": {
...
"primeng": "4.0.3",
"rxjs": "^6.3.2",
"rxjs-compat": "^6.3.2",
"tixif-ngx-busy": "0.0.8",
"zone.js": "^0.8.26"
}
and here is the error in console.
https://i.stack.imgur.com/RY565.png
migration angular6 rxjs6
migration angular6 rxjs6
asked Nov 11 at 11:08
Milind Kali
11
asked Nov 11 at 11:08
Milind Kali
11
edited Nov 11 at 11:24
asked Nov 11 at 11:08
Milind Kali
11
asked Nov 11 at 11:08
Milind Kali
11
asked Nov 11 at 11:08
Milind Kali
11
11
don't share code (including stack traces) as images. your exception is not visible / readable in attached screenshot. Instead copy paste your error to the question as text in readable fashion.
– muradm
Nov 11 at 20:41
add a comment |
don't share code (including stack traces) as images. your exception is not visible / readable in attached screenshot. Instead copy paste your error to the question as text in readable fashion.
– muradm
Nov 11 at 20:41
don't share code (including stack traces) as images. your exception is not visible / readable in attached screenshot. Instead copy paste your error to the question as text in readable fashion.
– muradm
Nov 11 at 20:41
don't share code (including stack traces) as images. your exception is not visible / readable in attached screenshot. Instead copy paste your error to the question as text in readable fashion.
– muradm
Nov 11 at 20:41
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Based on our troubleshooting related to this upgrade, We found out that, we were using an angular module called ngBusy that was causing the build to fail.
To be specific, here is how I troubleshooted this issue.
Narrowed down on files that might be causing the prod build to fail- I did this by starting with one module and testing if the build was fine or not and then added other modules one by one.
Based on step 1, I found out that if I remove all the occurrences of ngBusy, my angular build was working perfect, in both development and production environments.
Based on this, we upgraded the ngBusy module to version 6, which finally resolved the issue.
This was a very small issue but it took us, three days to dig it up. Hope it helps!
answered Nov 11 at 20:22
Mohd. Anas
1
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Based on our troubleshooting related to this upgrade, We found out that, we were using an angular module called ngBusy that was causing the build to fail.
To be specific, here is how I troubleshooted this issue.
Narrowed down on files that might be causing the prod build to fail- I did this by starting with one module and testing if the build was fine or not and then added other modules one by one.
Based on step 1, I found out that if I remove all the occurrences of ngBusy, my angular build was working perfect, in both development and production environments.
Based on this, we upgraded the ngBusy module to version 6, which finally resolved the issue.
This was a very small issue but it took us, three days to dig it up. Hope it helps!
answered Nov 11 at 20:22
Mohd. Anas
1
add a comment |
up vote
0
down vote
Based on our troubleshooting related to this upgrade, We found out that, we were using an angular module called ngBusy that was causing the build to fail.
To be specific, here is how I troubleshooted this issue.
Narrowed down on files that might be causing the prod build to fail- I did this by starting with one module and testing if the build was fine or not and then added other modules one by one.
Based on step 1, I found out that if I remove all the occurrences of ngBusy, my angular build was working perfect, in both development and production environments.
Based on this, we upgraded the ngBusy module to version 6, which finally resolved the issue.
This was a very small issue but it took us, three days to dig it up. Hope it helps!
answered Nov 11 at 20:22
Mohd. Anas
1
add a comment |
up vote
0
down vote
up vote
0
down vote
Based on our troubleshooting related to this upgrade, We found out that, we were using an angular module called ngBusy that was causing the build to fail.
To be specific, here is how I troubleshooted this issue.
Narrowed down on files that might be causing the prod build to fail- I did this by starting with one module and testing if the build was fine or not and then added other modules one by one.
Based on step 1, I found out that if I remove all the occurrences of ngBusy, my angular build was working perfect, in both development and production environments.
Based on this, we upgraded the ngBusy module to version 6, which finally resolved the issue.
This was a very small issue but it took us, three days to dig it up. Hope it helps!
answered Nov 11 at 20:22
Mohd. Anas
1
Based on our troubleshooting related to this upgrade, We found out that, we were using an angular module called ngBusy that was causing the build to fail.
To be specific, here is how I troubleshooted this issue.
Narrowed down on files that might be causing the prod build to fail- I did this by starting with one module and testing if the build was fine or not and then added other modules one by one.
Based on step 1, I found out that if I remove all the occurrences of ngBusy, my angular build was working perfect, in both development and production environments.
Based on this, we upgraded the ngBusy module to version 6, which finally resolved the issue.
This was a very small issue but it took us, three days to dig it up. Hope it helps!
answered Nov 11 at 20:22
Mohd. Anas
1
answered Nov 11 at 20:22
Mohd. Anas
1
answered Nov 11 at 20:22
Mohd. Anas
1
answered Nov 11 at 20:22
Mohd. Anas
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248105%2fangular-6-upgrade-run-time-issue-for-optimized-build%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
don't share code (including stack traces) as images. your exception is not visible / readable in attached screenshot. Instead copy paste your error to the question as text in readable fashion.
– muradm
Nov 11 at 20:41