fix(astro): Accessing import.meta at build causes app to break

[panteliselef]

Description

Pretty much what the title says

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

[changeset-bot]

🦋 Changeset detected

Latest commit: 282cce2

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

This PR includes changesets to release 1 package

Name	Type
@clerk/astro	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

[panteliselef]

!snapshot

[clerk-cookie]

Hey @panteliselef - the snapshot version command generated the following package versions:

Package	Version
@clerk/astro	0.0.2-snapshot.v282cce2
gatsby-plugin-clerk	5.0.0-beta.45
@clerk/testing	1.1.10-snapshot.v282cce2

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/astro

npm i @clerk/astro@0.0.2-snapshot.v282cce2 --save-exact

gatsby-plugin-clerk

npm i gatsby-plugin-clerk@5.0.0-beta.45 --save-exact

@clerk/testing

npm i @clerk/testing@1.1.10-snapshot.v282cce2 --save-exact

[wobsoriano]

I can confirm the error and it's probably the best to use the command property to check for the current environment instead.

Turns out, Astro config does not run inside Vite so import.meta.env won't work

[panteliselef]

I've verified with the snapshot that this PR fixes the issue.