Exporting a default component from an endpoint makes onPut unreachable

[mglikesbikes]

Qwik Version

0.9.0

Operating System (or Browser)

Cloudflare pages adapter

Node Version (if applicable)

No response

Which component is affected?

Qwik City

Expected Behaviour

Seeing some weird behavior with endpoints. Or rather — unexpected behavior. Consider the following:

// src/routes/test/index.tsx:

import { component$ } from '@builder.io/qwik';
import { RequestHandler } from '@builder.io/qwik-city';
export const onPut: RequestHandler = async () => {
  console.log(`you'll always see this`);
  return {
    success: false,
    error: "hello from onPut",
  };
};

const Index = component$(() => {
  return <div>hi</div>;
});

export default Index; <-- problem line

Calling it:

// src/routes/index.tsx
    <button
        onClick$={async () => {
          const res = await fetch("/test", {
            method: "put",
            headers: {
              "Content-Type": "application/json",
            },
            body: JSON.stringify({ foo: "bar" }),
          });
          console.log("-->", await res.json());
        }}>
        PUT
    </button>

Actual Behaviour

When the export default line is removed, onPut works fine. With that line in, I see the following:

• onPut() continues to invoke;
• onPut() does not return the correct value.

Screenshots below — first, the export default line is commented out and the fetch runs as expected. Next, I uncomment it and fire the fetch again after it's built in the background.

_`export default` is commented out, `fetch()` works fine_

_`export default` is commented in, `fetch()` explodes

Additional Information

As mentioned — I'm using the cloudflare pages adapter. I've deviated from the standard build scripts though, running the following in two terminals:

• qwik build (via npm-watch package, fired when files change)
• npx wrangler@beta pages dev ./dist --port 3000 (picks up changes to functions/ and dist/ and does whatever wrangler does to preview local content)