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
We have put in a work-around to fix the lack of informative errors. Should be self-explanatory:
// Re-trace simply crashes at random points if the stack is not valid// Try to provide a more detailed error messageif(error.message==='"version" is a required argument.'){thrownewError(`The source map is not valid or the domain URL is incorrect; Used URL: ${sourceUrl}. Original Error:\n${error.message}`);}elseif(error.message==='Response code 400 (Bad Request)'){if(minifiedStack.includes(' (<anonymous>)')){thrownewError(`Invalid Stack: Try removing line '(<anonymous>)'`);}}elseif(native.string.startsWith(error.message,'Protocol')){if(minifiedStack.split('\n')[0].includes(':')){thrownewError(`Invalid Stack: The first line resembles a URL. Try removing all colons.\nOriginal Error:\n${error.message}`);}}
It will be great to have this handled by the library itself as the hack above doesn't really work in all cases.
The text was updated successfully, but these errors were encountered:
This is a great tool BTW.
We have put in a work-around to fix the lack of informative errors. Should be self-explanatory:
It will be great to have this handled by the library itself as the hack above doesn't really work in all cases.
The text was updated successfully, but these errors were encountered: