Thank you for bringing this up. Apologies for the inconveniences for those that got problems with the latest plugin. We'll take a look at it and coordinate ourselves better with WebStorm upgrades. Unfortunately, you'll need to wait a bit for us to fix the problems. Thank you

Hi, @Albert Margarit (NS Eng Lead)! My past experience with SuiteCloud IDE for eclipse was not good. Issues related to "version lag" eventually made the software unusable. At the end, about two years ago, it wasn't even possible to download the version of eclipse package recommended in the documentation: it had actually been removed from the eclipse site and all the mirrors. When I eventually tracked down an installer on someone's hard drive, it turned out to be incompatible with the laptop (as I recall, a deprecated version of JRE). I kept trying. I started at the earliest available version of the recommended eclipse package and worked my up: download package, attempt to install, if it installs, see if it can execute, of OS allows execute, try to install SuiteCloud IDE, etc. Eventually I found one version that was partially supported by SuiteCloud IDE and partially by the OS (occasional crashes). In the end, what did I have? An IDE I never wanted to use in the first place + a partially functional plug-in. None of the SuiteCloud autocomplete or inspection functionality worked. It would hard to imagine UX/UI uglier and more arbitrary than what eclipse has on offer. This eclipse version was later than the NetSuite-recommended version, yet it could not support the version of JavaScript used by NetSuite's own compiler (ES2015, so the eclipse SuiteCloud IDE for the longest time didn't know words like

const

, struggled with object literal declaration, and could not parse many of the SS2.0 script templates included with the plug-in. So many stupidities: one had to do thing['delete']() because thing.delete() would cause a code-inspection meltdown. And the effort proved to be a total loss: of course I had to stop using SuiteCloud IDE, because it actually decreased my productivity. It was a broken tool built on a bigger broken tool. I settled for a decent text editor and forgot about it. A few weeks ago it occurred to me to check and see if the WebStorm version were available, and here we are. ANYWAY: I gave you the long and painful version of the story to emphasize how version lag can alienate users and kill adoption. I wasn't even paying attention when the WebStorm version became available (the SuiteWorld 2018 demo—how cruel that seems in retrospect). As a developer, I understand how and why maintenance activities may take a backseat to feature development. There is nothing sexy about release note auditing, static code analysis, and regression testing. As cyclic activities go, it's about as exciting as a changing HVAC filters. It's especially hard to balance the value "new functionality" against what needs to be done, when common-sense justifications like "keeping current" or "routine maintenance" are offered in lieu of an actual value proposition—and I think these commonplace terms downplay or even misrepresent the actual value of "keeping current" and "routine maintenance." What is it, then?

Hello Zach, I appreciate your comments. Just to give you some context, NetSuite is committed to bring development tools up to the level that they should. I do agree the state of the development tools is not great and hasn't been great for the past years. The Eclipse plugin and the first version of WebStorm was done with a really small team (2 people) for a few years, recently we created a full product team to just focus on development tools