feat: Add env param to Cloudflare Middleware

[nnelgxorz]

What is it?

• Feature / enhancement
• Bug
• Docs / tests

Description

Adds the Cloudflare env parameter as an envData render option. Allows users to access Cloudflare env variables in their Qwik City code.

import { useEnvData, component$ } from '@builder.io/qwik';

export default component$(() => {
  const secret_password = useEnvData('secret');
  //....
});

Discussion here: #1066

Checklist:

• My code follows the developer guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• Added new tests to cover the fix / functionality

[youngboy]

this is great, while I think it is a common pattern that user able to access middleware request's context. other framework like svelte exposed a property platform attach to specific adapter context.

1. for netlify, context have a useful util log and more in context, see https://docs.netlify.com/netlify-labs/experimental-features/edge-functions/api/#netlify-specific-context-object
2. this suggesting useEnvData is common way get runtime's ENV, user might be frustrating if it is not work for the middleware he is using if not implemented.

[nnelgxorz]

I agree @youngboy. What are your thoughts on improving this and making implementing it for Netlify and others?

[youngboy]

I agree @youngboy. What are your thoughts on improving this and making implementing it for Netlify and others?

maybe something like this ?

export const onGet: RequestHandler = ({ platform }) => {
   platform.context.log('netlify logging')
  // or in CF, platform.context.env('my-env')
};

[elxris]

@nnelgxorz I think this is a great and necessary feature but don't actually close the ticket I opened.

A PR that would actually close it would be to include the env context to the on___ request context.

[nnelgxorz]

@elxris I removed the closes tag from my PR. Going off of @youngboy's suggestion, here's a second WIP PR.

#1072

[nnelgxorz]

Closing in favor of #1072