Unexpected Temporal Dead Zone

[Ghirigoro]

Issue description or question

Is this issue related to Quokka not outputting the expected results of your code?: Yes

My code runs as expected when executed with node (using experimental type stripping) but fails when run in Quokka. The error is:

Cannot access 'string' before initialization

In this context, string is a schema factory function imported from another package in the same monorepo. The imports are plain TypeScript files, not bundled or transpiled.

Sample code

// apps/ush/src/data/test.ts
import data from "./placeholder.scenario.json";
import { USHScenario } from "./scenario.ts"; // This line causes the error

console.log(USHScenario.validate(data));
console.log(data);

Sample repository link

This is inside of a monorepo that would require a lot of files to reproduce. I'm happy to do it if necessary but I would first want to know that it's not some other more obvious issue (e.g. Quokka does not support packages that export TypeScript)

Quokka.js Console Output

Cannot access 'string' before initialization
@ src/data/test.ts:2:1

Code editor version

Visual Studio Code v1.104.1

OS name and version

OSX 15.6.1

[Ghirigoro]

For what it's worth this is what the offending string value looks like:

export const string = <const O extends SchemaFactoryOpts<string>>(opts?: O) =>
	schema<string, DefaultName<"string", O>, {} & O["properties"]>(
		defaultName("string", opts),
		[isString, ...(opts?.constraints || [])],
		{ ...opts?.properties },
		stringEncoder || opts?.encoder
	);

[smcenlly]

I would first want to know that it's not some other more obvious issue

There's nothing obvious in the sample you've provided.

Quokka does not support packages that export TypeScript

Are you using node_modules that export TypeScript files instead of JavaScript files? This is not expected and may cause a problem.

---

In terms of reproducing your problem, we shouldn't need your entire mono-repo. Are you able to reproduce the problem by moving the offending code to a single Quokka file? If the problem is with an import, you may need to introduce one other file (to import) to reproduce the issue with minimal amount of code.

[Ghirigoro]

Are you using node_modules that export TypeScript files instead of JavaScript files? This is not expected and may cause a problem.

Yes, I am. I get that this is an unusual setup and may not be officially supported, so I wouldn’t necessarily expect you to address it. Still, it’s worth considering. Turborepo, which is widely used, actually encourages this approach (docs). With TypeScript compilation getting faster and most runtimes (outside the browser) able to run it directly, I think this pattern will only become more common, especially in monorepos.

[smcenlly]

Are you able to reproduce the problem by moving the offending code to a single Quokka file?

[Ghirigoro]

Are you able to reproduce the problem by moving the offending code to a single Quokka file?

Sorry, I'm not sure what you mean. If the problem is that I am importing values from node modules that export raw typescript files, how would I simulate that in a single file?

[smcenlly]

@Ghirigoro - we weren't clear whether the issue is from importing from node_modules that export from a TypeScript file, or whether the issue caused by something else. If you know it's definitely caused by attempting to import the TypeScript file, then this isn't going to help.

If you can't reproduce the issue using a single file, are you able to do so using a publicly available npm package so we can see the issue for ourselves?

[Ghirigoro]

@smcenlly Just FYI:
I had a free moment this evening and I tried making a simple monrepo that has:

• pnpm workspaces
• An internal package that exports ts files directly (e.g. "exports": { ".": "./src/index.ts"}
• Another package that imports it and uses its contents

Quokka did fine on the package that imported the ts code so it's not that (or at least not just that). As my schedule permits, I'll start porting over pieces of the monorepo where the error occurred to see if I can recreate the error without making you all look through thousands of lines of code.