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
Is your feature request related to a problem? Please describe.
When there's a problem in the JS Parser and no output file(sbg-bindings.txt) is generated the build will just output a stack trace from the SBG for missing sbg-bindings.txt file, but will continue and an error will be thrown in runtime.
Describe the solution you'd like
In that case it would be better to stop the build, so that it would be more obvious where the problem is.
Additional context
In addition to that it would be good if we can easily get the errors from the JS Parser run either by starting only the JS Parser like this:
Is your feature request related to a problem? Please describe.
When there's a problem in the JS Parser and no output file(sbg-bindings.txt) is generated the build will just output a stack trace from the SBG for missing sbg-bindings.txt file, but will continue and an error will be thrown in runtime.
Describe the solution you'd like
In that case it would be better to stop the build, so that it would be more obvious where the problem is.
Additional context
In addition to that it would be good if we can easily get the errors from the JS Parser run either by starting only the JS Parser like this:
or by setting environment variable with
tns build android
like thisThe text was updated successfully, but these errors were encountered: