You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This error only occurs when we bundle our app - when unbundled, it just continues with no error.
Basically, if the app is bundled and a view require a css file that does not exist, the app crashes with a fairly unhelpful error message - and it gets even worse when minified: "b.replace is not a function":
Stepping through the code reveals that the css argument, which is normally a string, somehow becomes an empty object if the css file is missing - but again, it only happens when the app is budled:
The unhelpful error message aside, it's a really nasty surprise to encounter after making a release, so I would strongly prefer that it outputs a warning or error message both when bundled and unbundled.
Maybe just a warning when unbundled, so it doesn't get in the way of the dev workflow - reason for this is that e.g. the LESS compiler does not create a .css file unless the .less file produces non-empty CSS output.. so even though the .less file exists, it may not actually produce a .css file, either because the .less file is empty, or because it contains only variables or mixins, but not yet any style rules that would produce CSS output.
The text was updated successfully, but these errors were encountered:
This error only occurs when we bundle our app - when unbundled, it just continues with no error.
Basically, if the app is bundled and a view
require
a css file that does not exist, the app crashes with a fairly unhelpful error message - and it gets even worse when minified: "b.replace is not a function":Stepping through the code reveals that the
css
argument, which is normally a string, somehow becomes an empty object if the css file is missing - but again, it only happens when the app is budled:The unhelpful error message aside, it's a really nasty surprise to encounter after making a release, so I would strongly prefer that it outputs a warning or error message both when bundled and unbundled.
Maybe just a warning when unbundled, so it doesn't get in the way of the dev workflow - reason for this is that e.g. the LESS compiler does not create a .css file unless the .less file produces non-empty CSS output.. so even though the .less file exists, it may not actually produce a .css file, either because the .less file is empty, or because it contains only variables or mixins, but not yet any style rules that would produce CSS output.
The text was updated successfully, but these errors were encountered: