Switch order of parameters for CompileError constructor #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been hitting a problem in a
rollup
(v0.50) +buble
(v0.16) workflow: Error messages frombuble
are replaced with something more cryptic:As it turns out,
rollup
is calling theCompileError
constructor on its own, to decorateError
s coming from rollup plugins. But it calls the constructor with onlymessage
as its first argument, triggering the aforementionedTypeError
:I feel that the easiest workaround is to patch
buble
'sCompileError
constructor to be more alike theError
constructor.