sounds good

You could also (as of wrangler 3) use a

_worker.js

directory instead, where the

_worker.js/index.js

file is your normal worker, and anything in that directory isn't uploaded as a static asset

This isn't for the functions folder - this is using a

_worker.js

file which is a little different

is that a wrangler feature or a feature of Pages? I'm not using wrangler

@Walshy | Pages does the CI have wrangler 3 yet

we have not gone to wrangler 3 yet no

Ah, unfortunate. can't do that for now without pages publish then

the _worker.js exists before wrangler 3 though

but we don't document that haha

not the folder (in a working state)

yeah ok, a fix may have been in 3

is there a way I can tell what version of wrangler the CI is using?

I'd just go with this for now

yeah that sounds good

we're using 2.20.0

ah ok

I'm now getting a build error after assets are published:

Error: Failed to publish your Function. Got error: multipart uploads must contain a readable body_part or main_module

Are there any types available? I don't want them to be

any

for this typescript middleware

ts
const abTest = async ({ request, next, env }) => {
  const url = new URL(request.url)
  // if homepage
  if (url.pathname === "/") {

there's no

Middleware

types that I can see

Middleware is no different to a normal Functions context, is it?

Ah ok, so

const abTest: PagesFunction = async ({ request, next, env }) => {

is valid?

Yeah it should be

nice :)#

🙂

I'm really losing faith in being able to deploy to pages. I have a Remix app which regularly throws the

Failed to publish your Function. Got error: Error: Script startup exceeded CPU time limit.

error. I've tried to dynamic import everything where possible outside of the global scope, but this error frequently comes up on deployments... but randomly also works with no changes. It's becoming so regular that we're struggling to deploy changes without constant redeployment attempts. Lots of Googling really doesn't help, there just seems to be no way to debug or profile the code to identify where the issue lies 😦

Are there special rules around redirects to other domains? Nothing happens when the redirect is called? This is a middleware.

ts
const exampleShortenedUrls: ShortenedUrl[] = [
    { id: '2tg9xy3', url: 'https://example.com' },
    { id: '3f2tqv', url: 'https://en.wikipedia.org/wiki/Example.com' },
    { id: '48difn', url: 'www.google.com' },
];

...

    const { pathname } = new URL(request.url);
    const id = new URL(request.url).pathname.startsWith('/')
        ? pathname.slice(1)
        : pathname;

    const matchedUrl = exampleShortenedUrls.find((entry) => entry.id === id);

    if (!matchedUrl) {
        console.warn('Unable to find shortened URL', id);
    } else {
        console.info('Found shortened URL and redirecting user', id);
        Response.redirect(matchedUrl.url, 302);  // this does nothing?
    }

    return next();

"logs": [
    {
      "message": [
        "Found shortened URL and redirecting user",
        "2tg9xy3"
      ],
      "level": "info",
      "timestamp": 1685119189434
    }
  ],

When you say it does nothing... what is returned to the client? Does it fall through to the

next()

, return an empty response or something else?

the normal root of the page eg /

Oh I see now

You do

Response.redirect

but you don't return it