WebStorm 8 EAP (build 134.1081): Bower, improved spy-js and AngularJS support and more

Thank you for participating in WebStorm 8 Early Access Program! We started it almost a month ago and today we’d like you to try the next EAP build.

Download links you can find on WebStorm EAP page. This build is free and can be used for 30 day, not active subscription is required.

Here is a short summary of new features in it:

  • spy-js: seamless automatic proxy configuration on start, instant display of detailed call stack for selected event, autoscroll to trace option, exclude list for events and files you don’t want to trace, improved UI
  • AngularJS support: code assistance for ng-repeat and improved code completion inside {{}}, improved support for ui-routing
  • REST client improvements: Cookies
  • Bower integration: search through Bower registry, manage components in the IDE
  • RequireJS aliases support
  • Less 1.6 support

We’d also like to mention that we’ve implemented a workaroud that solves the issue with Node.js debugger: now by default node starts with –nolazy flag.

Read more about spy-js, Bower and REST client in this post. Or have a look at the release notes.

Spy-js

One of the most significant improvements in spy-js is an automatic system proxy configuration. Check this box when creating a new spy-js configuration and WebStorm will automatically enable system proxy to trace the events in your browser.

Note that there are some known issues with this automatic configuration:

    • On Mac OS X (starting from Mountain Lion) network settings change require user authorization, so when “Automatic system proxy configuration” is enables, you need to enter your admin password when starting/stopping spy-js to apply/rollback settings. You can disable the authorization with command:
      sudo chmod u+s /usr/sbin/networksetup
      (can be rolled back any time,  read more about it here).
    • Opera 12 on Linux needs the following (one-time) configuration: Preferences – Network – Proxy Server – Use automatic proxy configuration:
      http://localhost:<RC_configured_port>/spy-js-proxy.pac

Spy-js tool window usability was significantly improved:

  • Now you can almost instantly explore call stack for the selected event in the events list
  • With Auto-scroll to trace option enabled single click on the element in the middle of Event stack panel you can see the trace file in the editor window
  • With Exclusion list you can specify events or files that you don’t want to trace: add you custom exclusion rules or right-click on event and select Mute.

spy-trace

Bower integration

We added Bower integration available in Preferences | JavaScript. It allows you to:

  • see the list of components installed in your project;
  • update components;
  • search through bower registry and install new components.

bower

REST Client: we have Cookies!

In the built-in REST client we added Cookies support: you can add and modify cookies and see the list of cookies sent by the service. This feature allows you to handle service authorization and working with cookies much better while testing.

cookies

Download links you can find on WebStorm EAP page. We welcome your feedback in the comments and on our issue tracker.

Develop with pleasure!
- JetBrains WebStorm Team 

This entry was posted in Early Access Preview. Bookmark the permalink.

18 Responses to WebStorm 8 EAP (build 134.1081): Bower, improved spy-js and AngularJS support and more

  1. Áxel Costas Pena says:

    Any information about when will PhpStorm users enjoy the 134 branch?

  2. wallace souza says:

    Well done!
    One suggestion of mine is improve typing of ‘{{‘ for angularjs in html files, this could complete with ‘}}’, i saw this on sublime text and is useful

    • Ekaterina Prigara says:

      If you’re working with AngularJS project (you have angular.js in your project sources or angular.js is listed in project’s external libraries in WebStorm), you’ll have auto-closing of {{}}.

  3. Vladimir says:

    Hello. Where did “Single instance” checkbox gone?
    http://imgur.com/QLgZjV2

    • Ekaterina Prigara says:

      Hi,
      Now it’s in a Single instance mode by default. Could you please share with us a use case when you need multiple instance of one run/debug configuration running? Thanks!

      • Vladimir says:

        No, i’m asking because i actually need single instance and it doesn’t seem to work that way. This configuration compiles some scripts, starts a Nodejs server on port 8080, opens a browser and does some other crazy stuff. When i run it first time everything is fine. When i do some changes and trying to run it again a get an error:
        Error: listen EADDRINUSE
        which means what the port is in use. So now i need to manually stop the server and run it again.
        Before this EAP with “Single instance” checked WebStorm asked me about restarting the server if it was running. I pressed “Enter” and was happy :) Now i’m not.

        • Ekaterina Prigara says:

          Actually, what we tried to achieve is to make the behaviour with “single instance” checkbox checked default: offer you to restart the server every time and prevent you from seeing “listen EADDRINUSE” error.

          I found out that if you reuse an old configuration created in the earlier version of WebStorm and have “single instance” unchecked, in WebStorm 134.1081 you’ll still have it disabled, though you won’t know it/have option to check. I’ll file a bug.

          May it be your case? Please try to delete the old run/debug config and create a new one. Thanks!

          • Vladimir says:

            Ha, yes it was my case. I deleted old configuration and added it again. Now everything is working, thank you for the help.

  4. Hanni Sullivan says:

    During the installation of the EAP version I get asked whether I want to do a regular or a silent uninstall of my current version of WebStorm.
    If I remember correctly previous EAP versions could be installed in parallel to an existing version. The thought of uninstalling the stable version of a software in favour of the alpha one is a bit scary.

    • Ekaterina Prigara says:

      You should be able to install it in parallel, no need to uninstall the current version of WebStorm. Is this option available?

    • Ekaterina Prigara says:

      Update: unless the checkbox next to the stable version is unchecked, it won’t delete it (no mater whether a regular or a silent uninstall is selected). Sorry for confusing UI. We’ll fix it.

      • Hanni Sullivan says:

        Thanks for your quick reply.
        I should have added more information for you, sorry. A mere check box would not scare me as much as the radio button which force me to decide between a silent or a regular uninstallation of my WebStorm 7 instance.
        See for yourself: http://i.imgur.com/MgXKPeI.jpg

        Apart from this minor glitch, I’m really excited about WebStorm 8. I expect the same stellar work as usual. :)

  5. Hanni Sullivan says:

    Oh, never mind. I’m being stupid. I replied before my brain had correctly processed your answer. Sorry. I get it now.

  6. Pingback: IntelliJ IDEA 13.1 EAP 134.1160 is Available | JetBrains IntelliJ IDEA Blog

  7. Elior Boukho says:

    I also saw that you remodeled the Plugins menu, it is a lot better; however why did you remove the ability to sort plugins by update date? It was the way for me to check new plugins once in a while, but now I have to look at the whole list. This is really bothersome.

  8. Pingback: Welcome WebStorm 8.0: AngularJS support, spy-js, multiple selections, Grunt and more | JetBrains WebStorm Blog

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> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>