fix: avoid relying on Node specifics within compiler

[dummdidumm]

fixes #14294

[changeset-bot]

🦋 Changeset detected

Latest commit: 69ff33b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
svelte	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Rich-Harris]

preview: https://svelte-dev-git-preview-svelte-14314-svelte.vercel.app/

this is an automated message

[github-actions]

Playground

pnpm add https://pkg.pr.new/svelte@14314

[Ocean-OS]

Couldn't nullish coalescence be used here, like process?.cwd?.()??Deno?.cwd?.()??undefined?
I know it looks a little ugly, but it could look nicer with some line breaks or spacing (not to mention that the nested ternaries arguably look a little worse)

[dummdidumm]

No, that would throw if process was not defined

[Ocean-OS]

This will stop this error from happening, right?

[Ocean-OS]

This will stop this error from happening, right?

There still seems to be a bug, but it's a different one now

[razshare]

Would you say this is a commitment from the team? That is to say: not relying on node and runtime specifics for compilation?

I've been working on a project that makes use of a custom implementation of ES in order to compile svelte strings, and this took me by surprise when I tried to upgrade from v4 to v5.