fix(ssr): failed ssrLoadModule call throws same error

[TrickyPi]

Description

fixes #7030

Additional context

Is the new test file in the correct location?

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[bluwy]

The fix looks good to me, but I think the tests should be in packages/vite/src/node/ssr/__tests__/ssrModuleLoader.spec.ts to group the SSR tests.

[TrickyPi]

okay, done.

[Rich-Harris]

This is super nitpicky but this PR isn't quite in line with the behaviour of Node and browsers. If a module throws an error during instantiation, subsequent imports will throw the same error object:

let e1, e2;

try {
  await import('./bad.js');
} catch (e) {
  e1 = e;
}

try {
  await import('./bad.js');
} catch (e) {
  e2 = e;
}

assert.equal(e1, e2);

With this PR, the module is re-instantiated, and a new error is thrown. I was working on a PR separately, unaware this had already been submitted, and the solution I landed on was this — basically, store the error as mod.ssrError, and throw it in instantiateModule if it exists.