Dave Schinkel

Edited September 13, 2019 04:51

No it's mojave.  I also updated webstorm and it did not fix that original issue.  I see there's a mojave update out there that I have not updated yet to, let me try that next.

1. Community
2. WebStorm
3. React Import Name Collision with react.d.ts

• 0 votes

Created September 13, 2019 04:44

that's interesting, updated to 2.2 and now when I tell it to open my project, nothing happens, the welcome to intellij launch screen just sits there.

1. Community
2. WebStorm
3. React Import Name Collision with react.d.ts

• 0 votes

Created October 17, 2018 19:37

Yea was hard to find it at first because I had no idea what that "tag" was named in prefs.

1. Community
2. WebStorm
3. Get Rid of Code Tag Hints

• 0 votes

Created September 09, 2018 02:34

thanks that might have done it.

1. Community
2. IntelliJ IDEA Users
3. Running Tests Switches to Output Tab

• 0 votes

Created April 26, 2018 19:33

I've increased my memory to the following which seems to solve my issue.  Thanks for the other info though, I'll keep that in mind Elena! -Xmx2048m

1. Community
2. WebStorm
3. Memory Leak and Slow IDE When Editing Very Long .md files

• 0 votes

Created November 15, 2017 03:25

well I don't use or like Jest.  Oh well, doesn't make sense regardless.  Thanks

1. Community
2. WebStorm
3. expect not resolving in mocha even after mocha definitely type library added

• 0 votes

Edited October 17, 2017 04:29

actually this is funny, dumb mistake, the problem is that we weren't calling it `const updaterComponent = <UpdaterComponent>{component()}</UpdaterComponent>` works and debugs fine now. :P.  So...wi...

1. Community
2. WebStorm
3. Cannot Step Into Code at Breakpoints

• 0 votes

Created October 17, 2017 04:23

>Set breakpoint on a call to component() function yea that's going to do me no good, without jsx support this kinda sucks TBH.  That function is a callback, called by the render() of my container w...

1. Community
2. WebStorm
3. Cannot Step Into Code at Breakpoints

• 0 votes

Edited October 16, 2017 18:55

This code lives in a React Container.  Ultimately that code is in a method that's called during this container's render(): render render() { const { panels, seo, errors, coordinates, ...

1. Community
2. WebStorm
3. Cannot Step Into Code at Breakpoints

• 0 votes

Created October 02, 2017 18:14

I know that!  I'm saying you should give some kind of out, like a close this prompt or something.  I'm left with "? I guess I should just close this".  Not a very good user experience.  Better yet,...

1. Community
2. WebStorm
3. Report to JetBrains button Disabled

• 0 votes