fix(config): try catch unlink after load

[bluwy]

Description

While trying to run VitePress build on another project, there is a possibility for the bundled config to be called at the same time (same Date.now) based on this build code.

This sometimes cause Error: ENOENT: no such file or directory, unlink '/Users/bjorn/Work/oss/blas/vite.config.js.timestamp-1659938739266.mjs. This PR wraps the unlink in a try catch which works reliably for me.

Additional context

---

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.

[patak-dev]

Nice! This could explain the flakiness we experienced after the file name scheme change. I think there may not be possible to get a race condition between writing the file and doing the dynamic import, so this fix should work. Let's merge this one for now.

But maybe we should directly make sure we generate a unique name? Looks like we don't have a way to do UUIDs right now, so we could use a simple scheme as we do here

vite/packages/vite/src/node/ssr/ssrTransform.ts

Line 88 in c1fa219

let uid = 0

plus the current timestamp. I'm not sure if it is needed though, reusing the same file looks ok to me.

[bluwy]

Yeah I think this should now work fine too as it's not possible for two simultaneous call to have one unlinking first before dynamic importing. Though I'd agree that a unique name would be a lot safer if we implement one day.