Type declarations should work for package imports

[brandones]

@types/carbon-components-react doesn't provide types for ES package imports, e.g. carbon-components-react/es/components/UIShell. Typescript complains:

Could not find a declaration file for module 'carbon-components-react/es/components/UIShell'. '/path/project/node_modules/carbon-components-react/es/components/UIShell/index.js' implicitly has an 'any' type.
If the 'carbon-components-react' package actually exposes this module, consider sending a pull request to amend 'https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/carbon-components-react'ts(7016)

[floydjones1]

Can this be considered high priority? Is there any plans for brining typescript support directly from carbon-components-react instead of relying on @types/carbon-components-react. I'm finding that the types provided by @types/carbon-components-react is incorrect at times aswell

[Daveiano]

What is the state when using the new @carbon/react?

The page at https://github.com/carbon-design-system/carbon-components-react says we should use this package instead but there is no typescript support yet because @types/carbon-components-react is for the deprecated repo?

Also the documentation on https://www.carbondesignsystem.com/developing/react-tutorial/step-1 seems to be quite outdated?

[joshblack]

For TypeScript discussions, I made a discussion over at: #10752

This should be where teams can find the most up-to-date information on where our team is at with respect to TypeScript. At the moment, the types are community-provided and supported and we do not have influence over them. This is more of a logistics problem than anything else on our end, if teams would like to help I would love to chat more in the discussion.

Definitely am sorry that the situation for TypeScript is as rough and confusing as it currently is. It's definitely not our intention and we are trying to see what we could provide to improve this experience.

[tay1orjones]

Duplicate of #16436