I also remember this being a problem for me on some Chakra versions of 2.x.x but I have not had autocomplete work at all for v3
I believe jetbrains updated webstorm at some point to fix this issue because it was something to do with typescript? But I'm just throwing ideas out here

Hey @segunadebayo are you using vscode or webstorm. As I have mentioned, it works fine with vscode.

@segunadebayo JetBrains has made WebStorm available for non-commercial use. I would recommend taking a look at chakra-ui in it. A lot of the types feel like they're missing or not there at all when using the package via WebStorm (and others I'm sure)
Here's a list of issues that I have come across related to this discussion:

• Intellisense only works when the prop name has already been defined, but does not work on props themselves. e.g. will work for variant="(Ctrl+Space)" but not for <Button (Ctrl+Space) />
• Some components show has having no types at all, despite the documentation saying they exist. An example can be seen in this discussion with Drawer, but I have witnessed this with Tabs, Select, Fieldset, Field, and a lot more.
• Typing and intellisense in general takes a very long time to complete. I notice this whenever I add Chakra UI to a new project and it makes it frustrating to work with.
• This could very well be related to the rest of the intellisense issues, but createListCollection does not appear to type correctly when you are mapping through <collection>.items. Similarly, onValueChange's event type appears to be any.

I really enjoy working with Chakra UI. For my work and myself this is a no-brainer choice for theming. I just really hope this issue can be taken seriously for those trying to implement V3 into their workplaces.

Additionally I would like to note that V2 had this issue for a short period of time but it had gotten fixed. I am not sure if this means anything but worth noting.

I think this may be related to circular dependencies on the exports
For example, box.d.ts imports ChakraComponent from ../.. (index.d.ts) which imports ./components which imports ./box

Because when editing this manually to import ChakraComponent from ../../styled-system instead, I get the expected behavior:

I have done a bit of an investigation into this issue and was unable to fix anything by playing around in the source code.

My last though on this process would be to do some sort of post-build processes that includes the barrel import files after the fact rather than allowing typescript to pull from the barrel files to begin with. I'm going to play around with an implementation of this but I am not very familiar with open source contribution 🙏

Hey @nanoqoi were you able to figure something out?

Unfortunately I've been too busy to find an appropriate solution

Hey @nanoqoi thank you!