feat: Implement Astro integration

[blaine-arcjet]

This implements an Arcjet adapter for Astro. We do this via an integration that generates a virtual module, such that arcjet() gets added to the integrations array in astro.config.mjs with the normal SDK configuration. The integration then generates a client and types as the arcjet:client virtual module. This ensures there is a singleton client in the Astro module graph.

Closes #1075

[trunk-io]

😎 Merged successfully - details.

[socket-security]

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@astrojs/node@9.0.2	Transitive: filesystem, network	+2	78.6 kB	matthewp
npm/astro-integration@0.0.1	None	0	0 B
npm/astro@5.1.10	Transitive: environment, eval, filesystem, network, shell	+304	585 MB	fredkschott

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/emoji-regex-xs@1.0.0, npm/ofetch@1.4.1, npm/tinyexec@0.3.2

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[blaine-arcjet]

@SocketSecurity ignore npm/emoji-regex-xs@1.0.0
@SocketSecurity ignore npm/ofetch@1.4.1
@SocketSecurity ignore npm/tinyexec@0.3.2

[e-moran]

Looks great! Just have one question

[davidmytton]

Works really nicely. The docs will be good for this because there's several use cases we can show off.

I added some minor copy change suggestions. Also, when I started the server without a key I got quite a generic/scary error. If you look closely it explains the problem, but I was wondering if there's a more user friendly error we can throw instead? Or is this all Astro provides?

[blaine-arcjet]

Also, when I started the server without a key I got quite a generic/scary error. If you look closely it explains the problem, but I was wondering if there's a more user friendly error we can throw instead? Or is this all Astro provides?

I think we could enable env.validateSecrets via our adapter, but that might be too heavy-handed for all users? Perhaps we just document that it should be set.

[blaine-arcjet]

Setting this configuration produces this error at build time:

15:51:41 [ERROR] [config] [EnvInvalidVariables] The following environment variables defined in `env.schema` are invalid:

- ARCJET_KEY is missing

  Error reference:
    https://docs.astro.build/en/reference/errors/env-invalid-variables/

[davidmytton]

Overriding the default is probably not a good idea, so let's document it as a recommendation and also add the error description into our Troubleshooting docs. That way if someone searches, it's easy to find the answer.