No WebStorm IntelliSense for styled Ark components

[boar-is]

Description

Having the following code:

import { styled } from '../styled-system/jsx';
import { ark } from '@ark-ui/react';

const Button1 = styled('button');

Button1({
  type:
});

const Button2 = ark.button;

Button2({
  type:
});

const Button3 = styled(ark.button);

Button3({
  type:
});

Button3 has an intellisense ONLY for the panda properties (fontWeight, css, etc.), but not for the HTML properties (type, aria-*, etc.):

However, despite this, I still can't put arbitrary values to the HTML properties:

Button1 and Button2 work as expected:

The problem appears in WebStorm, when StackBlitz (Monaco/VSCode) looks fine.

Link to Reproduction

https://stackblitz.com/edit/panda-intellisense?file=app%2Fbutton.tsx

Steps to reproduce

The repro is a basic Next.js application with just Panda and Ark installed.

1. Clone the repro above
2. Open it via WebStorm
3. Go to app/button.tsx
4. Run intellisense dialog with Ctrl+Space for Button3
5. See the problem

JS Framework

React (TS)

Panda CSS Version

0.20.1

Browser

N/A

Operating System

• macOS
• Windows
• Linux

Additional Information

WebStorm 2023.2.5

Honestly, I don't know if I should address this issue here or to WebStorm (or maybe even to Ark). Let's start here.

[boar-is]

Also, Storybook render props are any.

const meta = {
  component: Button,
} satisfies Meta<typeof Button>

export const RenderedButton = {
  render: (props) => <Button {...props} />
}

I also noticed that it takes some time for the intellisense to even infer any, like it consumes a lot of resources.

[astahmer]

this looks like a WebStorm specific issue, as Panda just use Typescript to get autocomplete suggestions

[cschroeter]

@astahmer

Not sure, we also have a failing renovate PR for React types: #1719
Something is odd.

[segunadebayo]

I agree with @astahmer; this seems to be a Webstorm-specific issue. It works just fine in VSCode and StackBlitz

[segunadebayo]

@cschroeter

Not sure, we also have a failing renovate PR for React types: #1719 Something is odd.

The failing PR has nothing to do with this issue. It's mostly related to the next.js link

[boar-is]

I reached out to JetBrains support with another but similar issue. They told me I should track this issue and it's release is a "matter of weeks". I think it may fix this issue as well.