😦 TS should work when importing

.js

files and there's a

.ts

equivilant?

Does it not for you?

Do you mean importing

xy.ts

as

xy.js

should work (because at the time it's imported,

xy.ts

has already been transformed to

xy.js

)?

Yeah, exactly.

And Typescript should realize this and still give you autocompletion.

That's the way I've seen, at least.

Fantastic, let me try this real quick.

Importing

.ts

as

.js

still didn't work on the server:

11:10:10.125    ✘ [ERROR] Could not resolve "../credentials.js"
11:10:10.126    
11:10:10.126        ../../../buildhome/repo/functions/contact/index.ts:4:22:
11:10:10.126          4 │ import { Creds } from '../credentials.js';
11:10:10.126            ╵                       ~~~~~~~~~~~~~~~~~~~
11:10:10.126    
11:10:10.128    1 error(s) and 0 warning(s) when compiling Worker.
11:10:10.129    Build failed with 1 error:
11:10:10.129    ../../../buildhome/repo/functions/contact/index.ts:4:22: ERROR: Could not resolve "../credentials.js"

Maybe the working directly on local

functions

and on the server is different? But then again, importing

.js

files works just fine. Anyway, this is the file structure of my

functions

folder:

functions/
  contact/
    index.ts
_middleware.ts
credentials.ts

Lastly, this is the line where I import

credentials.ts

into `index.ts`:

import { Creds } from '../credentials.js';

Yes you can do this

If you compile a function into

/public/_worker.js

it will be uploaded as the Page function

Look at the outfile, the entrypoint, and then you can see I'm using esbuild-plugin-alias there too

I've noticed a possible bug where calling the same functions endpoint with different parameters at the same time at page load sometimes results in one or both functions crashing with error 1101. This only happens in deployed functions. Locally they never crash and when a page only calls a deployed function once, it never crashes, which is why I believe it is an issue with functions and not the code being run. As a workaround, I'm using client-side retries.

Hmm.. are you by any chance awaiting a promise in a global scope?

no

The multiple requests are coming from the same browser right? One browser makes multiple requests at the same time?

yes--I have pages on my site that call the same functions endpoint multiple times*

There is some kind of race condition going on in your code

Which leads to an uncaught exception.. I would catch all exceptions at the top level and return that in 500 response header.. so that you can easily see what the exception is when you reproduce it.

there is a top level catch, but I might not be processing that correctly--let me take a look

It is possible the runtime triggers the exception, in which case you can't catch it.. In that case I would stream the logs from your dashboard.

where in the dashboard can I view logs from pages functions? I must have missed it earlier

Logs tab

I don't have regular workers set up so I don't think I can access the logs tab

I created a regular worker and see the logs tab for it, but can't access logs for my pages function

I'll look into your earlier suggestion and report back if it seems to be a runtime exception

Ahh.. yeah ofc.. it is Pages.. :/

Maybe @User or @User know how to stream them through wrangler

npx wrangler pages dev

will stream all your `console.log`s to the terminal in local dev

Wait WHAT?!