WebStorm 9 Development Roadmap Discussion

We on the WebStorm team have drafted a WebStorm 9 development roadmap that we would like to share with you and get your feedback.

Please note the developed roadmap is not a finalized list of features that you’ll see in WebStorm 9. It’s pretty flexible and may be subject to changes. Furthermore, we haven’t included improvements in the existing features that we are planning to work on.

WebStorm 9 is planned for release in late 2014. Our Early Access Program will start a couple of months before the release.

The major issue that we are going to address in the upcoming release is WebStorm’s performance when working with large JavaScript projects. While this issue may not be apparent at first, it is quite complex and very important, and we work on it to make WebStorm faster and much more stable.

The highlights of the roadmap include:

We are going to finish our work on Yo integration (WEB-6744) and improvements in CSS3 support that we weren’t able to finish for WebStorm 8 release.
You can see the full list of features on the roadmap draft.

There is one more thing that we are currently investigating and would like your opinion on: possible PhoneGap integration. If you’re using it, how WebStorm could improve your experience with building mobile apps with PhoneGap? Please share your thoughts.

We’ll be very happy to hear your comments, idea and suggestions here or on our issue tracker where you can vote for issues or submit new feature requests.

Develop with pleasure!
JetBrains WebStorm Team

About Ekaterina Prigara

Ekaterina Prigara is WebStorm product marketing manager at JetBrains. She's passionate about new technologies, UX and coffee.
This entry was posted in Early Access Preview and tagged . Bookmark the permalink.

128 Responses to WebStorm 9 Development Roadmap Discussion

  1. Timo says:

    thanks for sharing your roadmap
    +1 for phonegap support
    +1 for editorconfig

    • Ekaterina Prigara says:

      We’re already working on improving existing 3rd party EditorConfig plugin.
      Do you use PhoneGap now? What features would you like to see in WebStorm for it?

  2. Ben says:

    +1 for phonegap/cordova support.

    I’m currently using Ionic (http://ionicframework.com/) heavily for my mobile angularjs applications and if phonegap support starts off, it may be possible to extend it to use Ionic.

    Automatic building upon file updates, instead of manually using cordova update through the cordova / ionic cli each time would be one feature great to have.

  3. Ben says:

    This is just a personal opinion, but it would also be nice if we can have official golang (http://golang.org/) support in webstorm.

    There’s a community built open source plugin, but it would be great if webstorm could perhaps back it / extend it to the standards of an official plugin.

    Go is gaining more and more momentum especially over these last few months – web frameworks are being released in alpha stage and those that have being using net/http (something along the lines of node.js for Go) in their production builds have seen success over the last year or so; this clearly displays Go’s productivity in web server development and future user increase.

    It would be great if webstorm eyes this trend and considers official investment / support.

    • Ekaterina Prigara says:

      Sounds interesting.
      At first sight the plugin seems quite mature. Are you using it? What do you think?
      What we do sometimes with community built plugins is that we contribute to the plugin. We don’t have such plans for Go plugin right now, but we’ll investigate this opportunity.

      • Ben says:

        Thanks for the reply,
        Yes, I am currently using the plugin – quite heavily since I code all my web servers in Go, yet I’m addicted to webstorm usage for all its goodness.

        One main problem/inconvenience would include being unable to convert the current project into one that’s compatible with Go – currently it’s only possible to recreate a project entirely as a Go project; only then after does Go compilation work.

        I recall a developer maintaining the plugin stating that they know this is a problem/inconvenience, but they just don’t know how to be able to customize the plugin to do such things.

        Expertise from the webstorm/jetbrains team to maintain and develop the plugin would seem to be of great help.

        Great to know that you’ll investigate into this and support in general. Hope all the best.

  4. Stanislav says:

    Full support of CommonJS modules and JSDoc (with markdown) would be great.

  5. Pipo says:

    I see JSDocs3 on the roadmap. More generalized doc notations would be very useful! While annotations like @ngdoc are very popular on Angular projects, dgeni (https://github.com/angular/dgeni) will result in even more custom annotations. It would be good to cover them somehow (e.g. currently @ngdoc is marked as a typo).

  6. MathRobin says:

    Great roadmap^^

    Maybe if I have something to suggest is an enhanced GitHub plugin. As the Atlassian Connector (https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+for+IntelliJ+IDEA), it could be very powerful if we can manage issues directly in the IDE.

    Or better integration of code coverage like using istanbul (see my ticket there : http://youtrack.jetbrains.com/issue/WEB-11221))

    Thanks for your great work :)

  7. CircleCode says:

    full support of requireJS would be great (with respect to path mapping from source to server, and so on)

  8. Niko says:

    +1 for Meteor support :-)

  9. Faz says:

    It would be great to introduce a support of CSS 3 features, inspired by this website I use every day : http://css3please.com/

    No more hesitation about prefixes.

  10. Alexey says:

    What about React/JSX support?

  11. crystian says:

    +1 for phonegap/cordova support. :)

    • Ekaterina Prigara says:

      What would be the top feature in PhoneGap support for you?

      • Jonathan Perl says:

        A nice start would be a scaffolding template and the ability to easily spin up the ios or android emulator.

        Famo.us is going to be coming out with their own phonegap / cordova bundler that packages the latest chrome — I think they are releasing it at next weeks HTML5 dev conference. It would be interesting to find out more details on that.

  12. +10 for Polymer support
    Cool framework, based on W3C standards.

    • Fabio Biondi says:

      I still don’t use Polymer but I’ll do it very soon.
      So anything useful for shadow dom, web components, HTML imports and AngularJS 2.0 (that will use these concepts) would be very very appreciated.

  13. Ray Shan says:

    All these look great but I’d love to see futher improvement in the UI/UX front. Many dialogs are very complex, with loads of info / options. It’s tough for beginners to get started, also tough for seasoned users since info overload = cluttered mind. Took me quite a while to configure Webstorm with minimal UI (no toolbar, no buttons, no status bar). It works really well now but still a lot of room for improvement.

  14. Michael Bielski says:

    It seems that with each iteration of the product the JSLint/JSHint processing takes up more and more cycles, and it is to the point that my instance of Webstorm locks for up to 15 seconds while linting. This is totally unacceptable on my primary development box (an I7 with 16g of RAM) let alone slower machines. I’ve also noticed that once it finds a lint error, it never seems to want to let go of it, forcing me to close and re-open the file. Anyway, would love to see improvements in this area.

  15. Fabio Biondi says:

    Hi guys, great work.
    Gulp, Meteor and Spy-js Node.js apps tracing are very interesting.

    I also use Phonegap and most of the problems are related to installation and configuration of the environment and SDKs, create builds, signing APKs, use simulators and debugging.
    In my opinion, none of these problems can be solved or helped by the IDE, except the debug.

    So the only thing that might be very useful (but Adobe and others are already working on something similar) would be the creation of an IOS/Android/Windows/RIM native applications that allows us to display a preview of our phonegap app directly from WebStorm to the device itself, to give us the ability to run, preview, debug and especially have a *live view* of the application while coding (something like Adobe Edge Inspect or Phonegap Developer App: http://phonegap.com/blog/2014/04/23/phonegap-developer-app/)

    You might think to add some widgets to:
    - manage Phonegap plugins (download, uninstall, reinstall or plugin list)
    - some CLI shortcuts (add platforms or create builds in one click and so on)
    - a panel to edit and change all the properties of config.xml, or the xml manifest
    - and so on

    But honestly none of these are really useful to me.
    Have you got something else in mind you want to share and discuss with us?

    • Ekaterina Prigara says:

      Thank you, Fabio, for your comment.
      To tell the truth, we are just starting to investigate the opportunities, so your feedback is very helpful for us.

    • Jonathan Perl says:

      Wow the phonegap developer app looks really nice. Thanks!

  16. CSS3 support please! What’s the EditorConfig change compared to the plugin? The bug link on the post is broken.

    I like the cordova integration idea too. Apart from a way to prepare/build from webstorm, how about some UI to install/uninstall plugins? Could have the same for platforms.

    • Ekaterina Prigara says:

      Thanks, fixed the link.
      Actually we are contributing to the existing plugin making it more stable, improving performance and adding some features.

      Yeah, seems that PhoneGap Build is what we have to start with… Thanks for ideas.

  17. sumanth says:

    1. Full support Web components / custom elements . WYSIWYG editor for custom elements , something like polymer designer project.
    2. More support for ES6/ES6 including annotations and async/ await. Angular 2.0 will use di.js which depends on annotations

    3. FRP like bacon.js
    4. Full support for ES6 modules i.e AMD , system loaders
    5. Sourcemaps for debugging traceur generated ES6 javascript files

  18. a user says:

    +1 for gulp
    +1 for meteor (!)

  19. Skandar De Anaya says:

    I agree
    +1 for phonegap support
    +1 for editorconfig
    +1 for CSS3

    I’m using phonegap already for a mobile project.

    Also there is Sailsjs MVC framework is getting popular and stable, it would be nice to support it please.

  20. Kristian Mandrup says:

    All the Web development vibe this year seems to be about:

    – Polymer Web Components (and x-tag)

    Finally they can be used and sure seem to be the future for how we develop web apps!

    Much of the workflow however is already supported by Bower, Yo etc. via generators and such.

    Would be nice with built-in snippets and auto-complete for typical polymer tags such as and including the attributes as per the API. Would also be cool with a “Create Polymer file” that creates a skeleton for a polymer element.
    The cool thing about web components is that it is mostly reuse/leveraging of existing techs, so not much extra to add beyond this to take full advantage!

    • Ekaterina Prigara says:

      Thanks for your comment.
      We was working on initial support for Web Components back in 2013 for WebStorm 7 release, now it’s clear that Polymer gains more and more attention in the community and we have to enhance its support in WebStorm.

      • I would love to see polymer support. Being able to “add new polymer file” where that file is a specific element, that would be amazing and make things easy.

        Another great way to do that, is to create the element ad-hoc in line in the html. Since the element would not be recognized, and see that this project has a polymer scope, I could use alt + enter to fix it by automatically adding a polymer element into the elements directory and immediately be able to edit that polymer element.

        Also, much like editing a block of injected code, being able to hit the same ‘edit injected code in window’ shortcut, could open that polymer element up into its own editable window.

        Those features would be amazingly awesome.

        Also, +1 for cordova/phonegap support. I would primarily use it for ionic. And would love to see the ability to have an automatic build system of some sort and to tell it to update/run the emulator.

        • Ekaterina Prigara says:

          Thanks for the suggestions. We most probably will take a look at Polymer and what we can do for the release.

  21. Hello,

    Will be great if you add database support into WebStorm as it done for PhpStorm. Web applications build on NodeJs and other frameworks includes works with database and this tool is very important for web developers.

    With regards,
    Iosif Peysakhov

    • Ekaterina Prigara says:

      We are thinking about it, however it doesn’t seem reasonable to add existing database tools since one usually use no-sql databases with Node.js. Have you tried Mongo plugin for WebStorm?

  22. uur says:

    Hi,

    Could you consider improving node-webkit support ?

    “require” statements in node-webkit little bit different than node context.

    Simple app structure;

    – node
    —- index.js
    – dom
    —- index.html
    – helper
    —- doe.js

    If parent file called from node context (index.js) than one must type like this;

    var john = require(‘../helper/doe.js’); ( relative to file )

    If parent file called from webkit context ( index.html );

    var john = require(‘./helper/doe.js’); ( relative to app root path)

  23. For those interested (all js devs should!) in AMD & CommonJS modules, it would be great if WebStorm supported [uRequire](http://urequire.org) .

    uRequire’s prime task is to convert CommonJs & AMD modules to UMD, CommonJS, AMD and a “combined.js” as a single .js file that runs everywhere (nodejs & Web).

    Among other features uRequire supports path translations (from 'models/Person' to '../../models/Person' depending on where it was required). It works standalone or with as a grunt plugin (grunt-urequire).

  24. interfaSys says:

    +1 for suppoting editorconfig
    +1 for CSS3 improvements
    +1 for Phonegap support

    Regarding Phonegap, the goal would be :
    - to add the features of the Phonegap plugin: http://plugins.jetbrains.com/plugin/7436?pr=phpStorm&showAllUpdates=true
    - to be able to initialise and build projects using Sencha Touch http://docs.sencha.com/touch/2.3.2/#!/guide/cordova
    - to easily change platform and build projects for several targets at once

    Check out the Visual Studio screenshots:
    http://docs.phonegap.com/en/2.3.0/guide_getting-started_windows-phone-8_index.md.html#Getting%20Started%20with%20Windows%20Phone%208

    • Ekaterina Prigara says:

      Thanks for your comment and links – we’ll have a closer look at new VS features for PhoneGap/Cordova.

  25. Nicholas Collins says:

    Personally, I would like to see better new project templates. For example, I may want to build a Node.js application, but don’t want to use Express. What I would propose is the ability to create a new project from Git/GitHub Repo address. Perhaps this is already on your roadmap as part of the enhanced Yo integration, but if not, I really would like to be able to create a new project from an arbitrary Git repo, where the repo would be cloned, introspected for project features (JS, SASS/SCSS, LESS, Stylus, Ruby, etc.), and loaded in WebStorm/IDEA.

    • Ekaterina Prigara says:

      You can totally do it right now. On the welcome screen select Check out from Version Control, select git and paste URL to the GitHub repo. It will be cloned and new project created.

  26. zoomclub says:

    Great to hear about interest in Cordova support! Phonegap’s developers had said that it was a “gap” solution until it became implemented everywhere else. I think this is now starting to happen and the best place for this implementation is directly in the IDE we already use.

    We are seeing more and more Cordova based solutions by companies like Ludei, Famo.us and others. I think this is a telling sign that the time to make this a part of the IDE experience has come. Just use the latest Webview as Famo.us and others are doing and make our day. If you want to provide the complete build server as another Jetbrains service, that sounds reasonable as well.

  27. Never heard of Gulp before, and I bet a lot more developers have heard of Meteor.

    Therefore, +10 for Meteor.

  28. Ag says:

    Guys, please stop adding controversial features. Keep our beloved editor light. Instead of adding new functionality, please keep polishing what we already have. Who really cares about Grunt or Gulp window, when all the tasks can be controlled through terminal?
    Ok, you’ve improved Coffeescript we do appreciate that, still there are tons of things that don’t work (like refactoring). Jade – awesome that we have support for it, but why does Webstorm get so incredibly sluggish with even considerably simple Jade templates? Same thing can be applied to Stylus files.
    Sorry for moaning, we do see the hard work you guys do, and we in fact appreciate that. Thank you very much for the greatest IDE.

    • Ekaterina Prigara says:

      This time the greatest efforts are going to be made to improve JavaScript performance. And we are constantly working on bug fixes in all existing subsystems as well.
      Thank you for your feedback. We appreciate it!

  29. Stephan says:

    Very happy to see support for Meteor in the works. Any chance to get famo.us on board, too?

    • Ekaterina Prigara says:

      Not for WebStorm 9, it’s a bit too early for us to consider famo.us support. 63000 are still in line before me for the beta :)

      • Stephan says:

        Today everything changes – May 19th is supposed to remove the need to wait in line for the rest of us ;-)

        • Ekaterina Prigara says:

          Tried Famous Starter Kit. Seems that everything works quite right in WebStorm – just download all the js files from CDN to add them to JavaScript External libraries in WebStorm. After that completion and navigation works fine + some inspections (good that guys added proper JSDoc for everything).
          Have you already tried famo.us?

  30. Ben says:

    I’d love to have to ability to create an “in memory” file. Seems Like I always have to keep sublime open next to intellij so I can play with a short script or take notes

  31. Kabir says:

    Meteor support sounds fantastic.
    What exactly would it entail?

    • Ekaterina Prigara says:

      We’ll first start working on predefined run/debug configurations for both server and client side of Meteor apps. Other features are still under discussion.

      • Dave says:

        Debugging would be awesome. Some other things I’d personally like to have are:

        - .html files automatically parsed as handlebars(or “spacebars”). Also related, Meteor’s handlebars implementation allows for attributes in inclusion lines, (ie. {{> something attr=5 attr2=”hello” }} and Webstorm currently marks these as errors when I change the parser for .html files to handlebars.

        - JS be aware of when you’re defining handlebar helpers so it knows if it’s “in use”

        That’s all I can think of right now, it currently works quite well after you set up library includes. Is this the best place to suggest such ideas should I think of anything else?

  32. Stephan says:

    I would love to see meteor support which also works with CoffeeScript. CoffeeScript is like a first-class language for meteor, so this feature would be natural.

    +1 for meteor-coffeescript

  33. Shkumbin Maksuti says:

    I really like Meteor, that’s why I voted for it. Meteor would be a top feature for WebStorm.

  34. mnemoniq says:

    I am a Google Dart user, I would love to see improvements in code highlighting/completion/analysis/etc for this language.

    • Alexander Doroshko says:

      I’m working on improvements in Dart code highlighting/completion/analysis/etc right now. To make sure that your favorite features have chance to be implemented and bugs fixed please file them in the issue tracker.

  35. J. Garon says:

    +1 for Meteor.
    This would be excellent since Webstorm has the same philosophy of a nice cohesive integration of different development technologies as Meteor.
    And it’ll line up to the release of Meteor 1.0

  36. Slava says:

    I am excited to see Meteor on the roadmap. Some ideas for WebStorm dev folks to consider as features where WebStorm can be much more superior than something like vim+meteor-cli:

    - Meteor reloads the server or the client if one of the source files changed. Right now Meteor is quite slow in noticing updates as it polls filesystem. I am sure WebStorm already has something similar and it can be faster in reloading programs.
    - Meteor doesn’t know how to inject new CSS on the page w/o reloading the whole page.
    - Meteor runs its server-side part in a node.js process. Debugging it appears to be harder for people as you need to find the right pid and connect the node-inspector. Also sourcemaps for server-side code sometimes fail to load properly for node-inspector. If WebStorm makes server-side debugging easier for people from day1, it would be huge win.
    - Template’s based layouts. Something like this smart package for Meteor: https://github.com/krevativ/Meteor-Xray

  37. +1 for GulpJS support
    +1 for PhoneGap support

    If it’s possible I’d really like to see some better code alignment options. Currently I’m unable to make:

    var a = 1;
    var ab = 2;
    var abc = 3;

    should auto-format to:

    var a = 1;
    var ab = 2;
    var abc = 3;

  38. spion says:

    I vote for improvements in TypeScript support. Since TypeScript 1.0 is out now, getting WebStorm 9 to be fully compliant with typescript 1.0 would be really awesome. Our company is seriously considering switching to Visual Studio just because of TypeScript support which is not quite there yet in WebStorm.

    • Ekaterina Prigara says:

      Constantly working on TypeScript support improvements and bug fixes. Are there any specific issues that you have with TypeScript support in WebStorm or is it just a general impression?

      • Drew Noakes says:

        +1 for TypeScript support. It’s an awesome language, but WebStorm 8′s support was seriously lacking. Lots of features are broken.

        I’ll keep registering problems in the issue tracker as I find them.

  39. chao says:

    I need PhoneGap support.

  40. mnemoniq says:

    If it’s possible I’d really like to mark/color a specific tab. Ideally I’d be able to right-click a tab and choose a color for it!

  41. Pingback: Running gulp tasks with JetBrains WebStorm | mrchief2000

  42. yovko says:

    +1 for phonegap support

  43. a says:

    Howdy would you mind stating which blog platform you’re working with?
    I’m going to start my own blog soon but I’m having a tough time deciding between BlogEngine/Wordpress/B2evolution and
    Drupal. The reason I ask is because your design and style seems different then most blogs and I’m looking for something completely unique.
    P.S Sorry for getting off-topic but I had to ask!

  44. mnemoniq says:

    Don’t forget Polymer Framework, seem to be used on a many awesome web projects and recently on the new UI web design Material Design from Google, and ported on Dart.

  45. timur says:

    + polymer support
    +1 for phonegap/cordova support.

  46. Rob Edgar says:

    One thing I would like to see is the ability to create plugins in js.

    Brackets/Atom both have very active plugin communities and are generating some really interesting and useful stuff simply because of the accessibility of js plugins. Useful WS plugins, outside of those developed by WS itself, are rare, tend to break quickly and are very poorly maintained.

    +1 for phonegap/cordova support.
    Not using it yet but company plans are to produce phonegap version of all our apps starting next year.

  47. +1 for Polymer support

  48. mnemoniq says:

    What about Git Branches for Multi-root Projects, i mean have multiple Git (submodule) repositories within a single project. Like in IntelliJ IDEA 11.1 ?!

  49. Josha Inglis says:

    +1 for Polymer support

  50. +1 for PhoneGap / Cordova
    +1 for Ionic
    +1 for polymer

  51. mnemoniq says:

    Maybe a VM options/Program arguments like in Dart Command Line Application configuration are pretty awesome !

  52. Tarun Elankath says:

    As a WebStorm customer, I’ll commit my cry to the clamour:
    +1 for polymer
    +1 for cordova/phonegap

  53. Cristian says:

    +1 for:

    Improved Dart inspection, + device (Android) debugging
    Polymer.dart
    Polymer

  54. jwjb says:

    I have been relying on Sublime Text which is a great text editor for developing in Meteor.js, but it will be wonderful to have an IDE offering as well with Meteor.js support coming in WebStorm 9 and if PhoneGap support was included that would make it even better.

  55. Thomas Amsler says:

    Polymer +1

  56. Pingback: WebStorm 9 EAP is Open! | JetBrains WebStorm Blog

  57. Scott Deeter says:

    I do a lot of Drupal work, but I’m starting to do more Meteor, so having support for it in WebStorm (PhpStorm) would be fantastic.

  58. Hasan Abo-Shally says:

    +1 Phonegap/Cordova support.
    +1 Polymer support.
    +1 Ionic support.

    +1 johnny-five maybe ;)

  59. filinto duran says:

    +1 for Polymer.

  60. Hi:
    Last Thursday, Meteor announced their support for PhoneGap/Cordova. They have a package that performs this integration which allows for showing the bundled “Mobile Meteor” app running on the desktop. It would be great:
    1. if that can be done from within Webstorm 9.
    2. Also would be great to support the Meteor syntax that calls Cordova APIs.

    Links:
    youtube accouncement: https://www.youtube.com/watch?v=zzNoXbv1DX4&feature=youtu.be&t=24m32s

    demo: http://solomo.meteor.com/

    thanks,
    M

    • Ekaterina Prigara says:

      Hi, thanks, we keep an eye on Meteor updates and will see what we can do to make our Meteor support (that we’ll be introduced in the upcoming EAP build) even better.

  61. aaron says:

    Very interested in the Meteor story too.

    The new Meteor 0.9.x packaging system, cloud deployment, helpful templates for a jump-start, and some project reference (code/file) intelligence (I’m thinking something close to MS intellisense).

    Meteor debugging is very important of course.

    Integration with Meteor’s new front end templates and libraries/frameworks Blaze, Spacebars, along with the up and coming Famo.us is a must.

    As every, continue to improve your MongoDb integration.

    Speed everything up (maybe by removing old code/routines/libraries or by breaking off a Node/JavaScript and Node related tools from the rest of the IDE — making it specialized to the MEAN/Meteor stack).

    And — for gosh sake — add skinning support or make it trivial for others to do so!

  62. Alexander says:

    must-have would be support for:

    Polymer
    Akka

    also nice would be support for:

    Panamax
    Apache Brooklyn
    Hystrix

  63. arcseldon says:

    +1 phonegap / ionic / cordova tooling support.

    Webstorm is an awesome IDE. However, agreed, the performance in webstorm 8 with large codebases degrades, really happy to hear this is being addressed. Currently, for multi node projects, you cannot really do npm install on more than one project at a time. This is painful as having 15 projects all requiring an update say when a commons (custom) NPM module is version upgraded, doing it in serial order via webstorm is no good. Have to use ITerm etc and drop using webstorm altogether. Hope to see this fixed too. If you can fix up the screen flicker (project modules view) when doing npm install too that would be nice – currently lose the mouse cursor while the event thread is busy with the install, and the View refresh flashing is a bad user experience.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">