Dist types now require @types/ts-expose-internals about ts-json-schema-generator HOT 9 CLOSED

I think it makes sense that you get the /// ... ref import when you have a type only import. That's probably what's going on so I think we should make ts-expose-internals a dependency or remove it from the package.

from ts-json-schema-generator.

Where is this error being thrown?

This is probably because you have "skipLibCheck": false in your tsconfig, is there a reason for also type checking your dependencies?

from ts-json-schema-generator.

Dependencies should type check if possible.

from ts-json-schema-generator.

Hmm, somehow tsc is adding this directive on every dts file emitted...

Have to say, never saw something like this before, I cannot even find documentation about it.

from ts-json-schema-generator.

I think typescript is adding this triple slash directive every time ts is imported/used. As the ts-expose-internals library extends the typescript namespace, it thinks without this definition some code would be invalid (which is incorrect).

We could simply add ts-expose-internals as a dependency, but this would fuck up every library that uses this package by also having the extended types for them.

I'm currently looking up for a solution but this is an undocumented behavior of typescript. Probably having to disable type check or manually removing these /// ... references are the solution here....

from ts-json-schema-generator.

Hi i have seen that in some files the import of typescript got changed from import ts from "typescript"; to import type ts from "typescript"; might this be the problem ?

from ts-json-schema-generator.

I don't think so, import type is just a way to say that all imports are only used in the type land and aren't present in the final js code.

from ts-json-schema-generator.

HI yes that fixed the problem thanks for the quick solution

from ts-json-schema-generator.

🚀 Issue was released in v2.3.0 🚀

from ts-json-schema-generator.