Pascal Garber

Good point. It should definitely be documented and maintained somewhere. Maybe we can tag types in the comments with @version @deprecated tags and then support a wide range of GJS...

@vixalien Unfortunately, we have not yet updated the documentation on the main branch, but hopefully this will happen soon. The option is still available in the 3.x branch. On the...

@vixalien I have removed the option because it should not absolutely necessary for your case and this simplifies the maintenance effort. You can still generate the types, with the difference...

@vixalien Thanks for the feedback, I have a few more questions about your use case: Do you write your sources in TypeScript? And if so, how do you transpile the...

I have now created a working example that shows how to generate the types by yourself and use them to create a simple GJS application with `tsc` and `npm`: https://github.com/gjsify/ts-for-gir-local-tsc-example...

And here an almost identical example, but uses `esbuild` instead of `tsc` to build the TypeScript code: https://github.com/gjsify/ts-for-gir-local-esbuild-example The example also uses the direct `gi://*` imports, but thanks to esbuild...

You can find more examples in the `ts-for-gir` repository, including some that use `esbuild`, `Vite` and `Webpack` as bundlers, with `gi://` or `@girs/*` imports (so both usages are demonstrated). The...

@vixalien Did my examples help you or do you think it would be better to read support without package.json?

@vixalien Okay then I will try to implement it again to be independent of a `package.json` and a bundler. But I can't say just yet how quickly this will happen

This was not a conscious decision, but does not cause any problems as far as I know, if you think it can be cleaner I am happy about suggestions :)