Support globalThis in getGlobal() for better compatibility

[simonihmig]

globalThis is the actual ECMAScript standard for the global object, so this should be returned by getGlobal() when available. The existing code (taken from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis) is good as a replacement when globalThis is not available, but when it is, we should return it directly! See a similar example in Ember.js.

This fixes a real world issue I had when running xstate in a rather exotic environment (GraalVM running JS inside a Java server), which correctly supports globalThis, but does not support global (which is node.js specific!) or self.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0d51d33

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

This PR includes changesets to release 1 package

Name	Type
xstate	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

[ghost]

CodeSee Review Map:

Review in an interactive map

View more CodeSee Maps

Legend

[davidkpiano]

This makes sense to me. @Andarist Any unforeseen issues?

[Andarist]

I wouldn't predict this setup 😅

GraalVM running JS inside a Java server

but the change looks OK - I'm glad it fixes a real issue 👍 didn't know that there envs that only support this as a "global" variable

[simonihmig]

didn't know that there envs that only support this as a "global" variable

AFAIK globalThis is the only global object that is defined in the ECMAScript spec itself. So from an engine's standpoint, this choice probably makes sense.

Anyways, thanks for the quick review and PR acceptance! 👍