Fetch init.signal error

[WcaleNieWolny]

Error: packRequest: init.signal
    at packRequest (blob:null/74878e83-1a35-4f3c-a67a-93d94adee03e:1003:50)
    at blob:null/74878e83-1a35-4f3c-a67a-93d94adee03e:765:22
    at fetchWithTimeout (blob:null/b9119e73-2aec-4ae2-bd38-1b596890bc68:32228:28)
    at fallback (blob:null/b9119e73-2aec-4ae2-bd38-1b596890bc68:32263:29

Code to reproduce:

async function fetchWithTimeout(resource: RequestInfo, options: RequestOptions = {}): Promise<Response> {
  const controller = new AbortController()

  console.log('fetch', resource)
  const { timeout = 5000 } = options
  console.log('timeout', timeout)

  const id = setTimeout(() => {
    console.log('timeout')
    controller.abort()
  }, timeout)
  const response = await fetch(resource, {
    signal: controller.signal,
  })
  clearTimeout(id)
  return response
}

Line causing: here

[johnspurlock-skymethod]

Yes, right now in local serve, the fetch over isolate rpc doesn't support the signal param in fetch options.

While you are waiting for this to implemented, you can serve your worker locally without the isolate sandbox using serve's --local-isolation none option. Note this will also disable hot-reload so you'll have to restart the process on any changes.

[WcaleNieWolny]

I do not think I can to be honest

[johnspurlock-skymethod]

hmm, try providing a full path in the config for "main"

[WcaleNieWolny]

{
  "$schema": "https://raw.githubusercontent.com/skymethod/denoflare/v0.5.12/common/config.schema.json",
  "scripts": {
    "main": {
      "path": "./main_router.ts",
      "localPort": 3030,
      "bindings": {
        "STRIPE_WEBHOOK_SECRET": {
          "value": "test"
        },
        "STRIPE_SECRET_KEY": {
          "value": "test"
        },
        "API_SECRET": {
          "value": "testsecret"
        },
        "PLAN_MAKER": {
          "value": "test"
        },
        "PLAN_SOLO": {
          "value": "test"
        },
        "PLAN_TEAM": {
          "value": "test"
        }
      }
    }
  }
}

Here is how my .denoflare looks. It work perfectly without this flag. Let me know how I should change this

[johnspurlock-skymethod]

change "path": "./main_router.ts", to a fully qualified path

in general, denoflare can be called from any directory using named config scripts like this

[WcaleNieWolny]

So an absolute path?

[johnspurlock-skymethod]

Ah, I'm able to reproduce only if I'm running denoflare in "no-install mode"

i.e. deno run --unstable --allow-read --allow-net --allow-env --allow-run
https://raw.githubusercontent.com/skymethod/denoflare/v0.5.12/cli/cli.ts serve x

the import statement is considered relative to the running remote script path in this case

workaround for now is to try and prefix your absolute path in the config with file://

I'll add a separate issue for the --local-isolation none mode not working when running in no-install mode as a new issue

can you verify your denoflare setup and also your os environment and output of deno --version