Typescript and intellisense issues with Yoga npm package version 2.0.0-beta.1 about yoga HOT 4 CLOSED

It seems like your tsconfig is not configured to allow TypeScript to resolve the “package.json” exports field.

This can be set using the “moduleResolution” option in your tsconfig. I would recommend “bundler” if you are using TypeScript 5, otherwise an option like “node16” or “nodenext” should work.

from yoga.

That does work for Typescript users, but what about Javascript users? They will have no tsconfig file. For example, my Visual Studio Code examples apply to Javascript users. They will essentially have no intellisense. Maybe that should be left for IDEs to implement though.

Do you think adding an index.d.ts file would be incorrect? I've never really dealt with type definitions and export maps in other projects.

from yoga.

I had originally had an extra “index.js” and “sync.js” files to try to catch clients which weren’t configured to support the exports field, but it ended up instead seeming like more churn than worth it.

It effectively means that you can transparently get opted out of platform conditions, and makes it very easy to get mismatched types from source.

I think the field will continue to become more common, and new out-of-the-box tsconfig for Node and frameworks do now tend to choose a compatible option. https://github.com/tsconfig/bases/tree/main/bases

As that continues, I would expect that VSCode learns to do ES Module resolution when a configuration file isn’t present, but IDE usage of types in an otherwise untyped project isn’t something I’ve tried to really test.

from yoga.

Cool, sounds good, I'll close the issue.

from yoga.