0.9.4 breaks some Typescript configurations

[djMax]

Description

Something in the changes in 0.9.4 causes NodeNext module resolution to fail.

#1634

Reproduction

Node.js side, but build time so no reason browser wouldn't also be affected. I can't get the playground to fail because I don't have full control of tsconfig it seems, but here's what fails in a local build with specific tsconfig values (as described in the discussion):

Playground

Expected result

URLs should be "known" but end up just being ignored/allow any value.

Checklist

• I’m willing to open a PR (see CONTRIBUTING.md)

[drwpow]

Thanks for the investigation! Looking into it. It could have something to do with a change to openapi-typescript-helpers. I think I’m going to add tests for different moduleResolutions somehow. Could or could not be the problem based on #1634, but couldn’t hurt to eliminate that as a possibility. This seems like a bug, as TSConfig settings shouldn’t affect type safety.

[djMax]

Let me know if I can help - I had a sniff that the helpers might be involved too but I couldn't quite see how. There are a number of typing related changes in there, so it's a bit beyond my limited current understanding of the type infra here.

[djMax]

Is this theoretically fixed? I think it is but I have only seen that the playground errors now (as it should). But before I go through the variety of deps to update would love to know it was intentional :)