EmberJS: Some errors not thrown in production
up vote
0
down vote
favorite
Recently I encountered a scenario where an error (Assertion Failed: calling set on destroyed object) was thrown while running my app in development mode, but the same error wasn't thrown in production.
Why is it so? Is there a justification?
If I'm missing, what other differences between production and development mode should I know?
ember.js ember-cli
asked 2 days ago
karthikaruna
457419
add a comment |
up vote
0
down vote
favorite
Recently I encountered a scenario where an error (Assertion Failed: calling set on destroyed object) was thrown while running my app in development mode, but the same error wasn't thrown in production.
Why is it so? Is there a justification?
If I'm missing, what other differences between production and development mode should I know?
ember.js ember-cli
asked 2 days ago
karthikaruna
457419
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Recently I encountered a scenario where an error (Assertion Failed: calling set on destroyed object) was thrown while running my app in development mode, but the same error wasn't thrown in production.
Why is it so? Is there a justification?
If I'm missing, what other differences between production and development mode should I know?
ember.js ember-cli
asked 2 days ago
karthikaruna
457419
Recently I encountered a scenario where an error (Assertion Failed: calling set on destroyed object) was thrown while running my app in development mode, but the same error wasn't thrown in production.
Why is it so? Is there a justification?
If I'm missing, what other differences between production and development mode should I know?
ember.js ember-cli
ember.js ember-cli
asked 2 days ago
karthikaruna
457419
asked 2 days ago
karthikaruna
457419
asked 2 days ago
karthikaruna
457419
asked 2 days ago
karthikaruna
457419
asked 2 days ago
karthikaruna
457419
457419
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
Assertions are removed from production builds. All "assertion failed" errors should be addressed during development. Also production builds are usually minified and fingerprinted.
answered 2 days ago
Gennady Dogaev
3,8271818
3
it should be noted that this is to improve performance in production.
– Lux
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Assertions are removed from production builds. All "assertion failed" errors should be addressed during development. Also production builds are usually minified and fingerprinted.
answered 2 days ago
Gennady Dogaev
3,8271818
3
it should be noted that this is to improve performance in production.
– Lux
2 days ago
add a comment |
up vote
3
down vote
accepted
Assertions are removed from production builds. All "assertion failed" errors should be addressed during development. Also production builds are usually minified and fingerprinted.
answered 2 days ago
Gennady Dogaev
3,8271818
3
it should be noted that this is to improve performance in production.
– Lux
2 days ago
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Assertions are removed from production builds. All "assertion failed" errors should be addressed during development. Also production builds are usually minified and fingerprinted.
answered 2 days ago
Gennady Dogaev
3,8271818
Assertions are removed from production builds. All "assertion failed" errors should be addressed during development. Also production builds are usually minified and fingerprinted.
answered 2 days ago
Gennady Dogaev
3,8271818
answered 2 days ago
Gennady Dogaev
3,8271818
answered 2 days ago
Gennady Dogaev
3,8271818
answered 2 days ago
Gennady Dogaev
3,8271818
3,8271818
3
it should be noted that this is to improve performance in production.
– Lux
2 days ago
add a comment |
3
it should be noted that this is to improve performance in production.
– Lux
2 days ago
3
3
it should be noted that this is to improve performance in production.
– Lux
2 days ago
it should be noted that this is to improve performance in production.
– Lux
2 days ago
add a comment |
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%2f53372822%2femberjs-some-errors-not-thrown-in-production%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
