Reserve error stack information

[LongTengDao]

This PR contains:

• bugfix
• feature
• refactor
• documentation
• other

Are tests included?

• yes (bugfixes and features will not be merged without tests)
• no

Breaking Changes?

• yes (breaking changes will not be merged unless absolutely necessary)
• no

List any relevant issue numbers:

Description

Help to find where the error occurred from the plugin.

[lukastaegert]

Hi @LongTengDao,

thanks a lot, having the original error stack is much better!

However to make the code a little simpler and rely less on the formatting of the error stack, I do not think it is necessary to combine both error stacks. After all, plugin developers only care where the error was thrown in the plugin and not where it was handled in Rollup, so how about just doing something simple like

let msg = `Could not load ${id}`;
if (importer) msg += ` (imported by ${importer})`;
msg += `: ${err.message}`;

const error = new Error(msg);
error.stack = err.stack;
throw error;

i.e. just copying the stack from the old error to the new error? The advantage would be that this code no longer relies on the exact wording of the error stack (which might break in future Node versions?)

[LongTengDao]

@lukastaegert Hi!
If we don't need new stack, how about directly using the old error object, not to create it here any more?

[lukastaegert]

You are right, we could just change the message 👍

[LongTengDao]

@lukastaegert Done~

[lukastaegert]

👍