On Tuesday, March 26, we’ve held a free webinar where JetBrains Technical Evangelist for PHP and .NET Maarten Balliauw went through the most important features of the latest PhpStorm 6 release. The recording of this webinar can be found on our YouTube channel. (more…)

Every JavaScript project bigger than "Hello, World" one uses libraries, often many of them. That's why handling libraries properly is so important for the IDE. Let's look at how WebStorm 6 supports libraries and what have been changed since version 5. If you haven't played with libraries lately, or just want to refresh memory, please take a look at our previous posts. And you can try all this in the recent WebStorm release. (more…)

One of the evolutions in JavaScript development is the new TypeScript language, an open-source superset of JavaScript that allows us to write code in a typed language which compiles to JavaScript. At JеtВrаins wе wоrk tirеlеssly tо bring аbоut mоrе аnd bеttеr suрроrt fоr this lаnguаgе. WebStorm 6 introduces full support for the TypeScript language through 3 new features: File Watchers, Sourcemaps and general support for working with code. (more…)

In WebStorm 5.0 we've introduced new JavaScript static checks and editor intentions to improve your coding experience. Besides checks produced by JSDoc annotations described in the previous post, some fresh inspections for JSON, jQuery selectors and other contexts have been added. (more…)

Today's post is about a nice feature set (many of you have been using for a long time) and its recent improvements. I'm talking about static type checking when type of parameter or variable on the left side of assignment or function return type is explicitly specified in JSDoc annotation. For 5.0 release we've supported Google Closure types syntax, so that quite complex situations can be handled more accurately and conveniently. To start with let's consider the most basic situation: (more…)

Hi JavaScript devs! There's no doubt that everyone is using one or another library to access/manipulate the DOM, and jQuery is currently the most popular one. And WebStorm has lots of small but really neat features to help you coding. Let's quickly get a feeling of what we have. 1. Selecting DOM elements The first thing you usually do is selecting some DOM element(s), right? WebStorm will help you with completion for the most used selector types, such as elements ID-s: or CSS classes: Sure you can use more complex selectors, which are also supported, like mixed matching:

Providing comments and annotations to your JavaScript code is a way to make it more definite and easier to read by other developers. It is especially important in large projects. Some static code analysis tools and verifiers take types and other information provided in JSDoc tags into consideration and report warnings if code is inconsistent with annotations. We suggest you as developers to developers to use annotations as much as possible. JSDoc tags support in PhpStorm/WebStorm 5.0 has been improved to make your coding experience better. When something is known about current context, more

Measuring JavaScript code coverage naturally complements unit testing. It provides a clear picture of which parts of your code remain untested, and helps you focus additional tests on the uncovered code. From now on, users of JsTestDriver can measure code coverage visually, right in the editor. (more…)

As you may know from the previous post about JavaScript libraries in PhpStorm & WebStorm, the main benefit of specifying JavaScript libraries in your project is to populate a completion list with only relevant members. We have reorganized the configuration panel at Settings|JavaScript|Libraries, so it hopefully become easier to use. If you simply want to select a library for the whole project, check the corresponding box. For more complex library scopes configuration, click Manage Scopes... button. Also, for per-file scopes settings, you can use JavaScript file context menu trigg

We are getting a lot of reports and ideas from you about the ordering of JavaScript completion options. So in WebStorm 4.0 and PhpStorm 4.0 we made small but important improvements. More relevant suggestions now appear at the top of the list in many cases. (more…)

This week's EAP brings you important bug fixes and improvements in all areas, with following changes most notable: PHP 5.4 is now fully supported - this build will recognize trait use section's method renames and conflict resolution rules and infer $this type in closures. There still some minor things to refine.. Anyway please pay attention to problems with 5.4 features and file all reports as new separate issues PHP "Language Level" setting is added to project - see Settings | PHP. It will also set features for Language Level inspection to mark as unavailable PHPDoc inheritance suppor

As you may know, there are different versions of the JavaScript language. Each JavaScript engine implementation adds some nice features that others don't have. To make sure that you only use features suitable for targeted environments, choose an appropriate one in Settings | JavaScript. (more…)

If you're a JavaScript developer, you probably know that the quality and correctness of your application are crucial. Well, consistency and regression testing just got a little less painful. Meet JsTestDriver plugin - an open-source project that was originally started at Google and is now contributed to by the JetBrains team. WebStorm 3.0 bundles it. Users of other JetBrains IDE - PhpStorm, IntelliJ IDEA, PyCharm, RubyMine, and AppCode - can install it from the plugin repository following these instructions. It allows you to enjoy all the benefits of JsTestDriver right from the com

We're glad to announce a new code analysis feature that is available in the most recent PhpStorm EAP— Locate Duplicates. This feature lets you quickly find duplicate code fragments and then fix them, therefore reducing the size of your code and making it easier to understand and maintain. (more…)

If you like the mixture of JavaScript and coffee and have jumped on the boat of CoffeeScript adopters, then this piece of news is for you. First EAP of PhpStorm & WebStorm 3.0 bundles new and improved version of CoffeeScript plugin that was originally started by Michael Kessler under name ‘CoffeeBrew’ and is now taken over by JetBrains team. The new version adds code navigation and completion and rename refactoring to the previously available syntax highlighting and error checking for coffee files. And we just started - the next EAP will bring you more cool stuff, such as Find

Both WebStorm 2.0 and PhpStorm 2.0 allow you to debug JavaScript code while running it in Mozilla Firefox (including Firefox 4). In WebStorm 2.1 and PhpStorm 2.1, which are currently in early production access, you can also choose to debug JavaScript in Google Chrome. Debugger for Chrome supports all features of JavaScript debugger for Firefox. You can set breakpoints, inspect local variables, evaluate expressions and more: If you use Chrome for web browsing and want to debug in it simultaneously, you can configure WebStorm or PhpStorm to use a separate Chrome user profile in ‘IDE Sett

JavaScript libraries introduced recently are very well accepted by you. And it is just the time to make one step further to ease your work with JavaScript. Now, in the recent 2.0 build, you can open a Web page with API documentation for an external library class or function at caret position by pressing Shift+F1. This works for the following frameworks: jQuery/jQuery UI Dojo ExtJs Prototype Mootools Scriptaculous Yahoo UI 3.x (more…)

Recently JavaScript specification was incrementally advanced with: a) common coding pitfalls prevention mode (aka "strict mode") and b) nice (yet de-facto already used) existing library additions. With several browsers around the corner completely supporting new-but-backward-compatible standard we are HAPPY to announce that WebStorm 2.0 (and PhpStorm 2.0 too) will help YOU to use these new productive stuff! The good news is that when your code uses "use strict" (example on the left), the editor will mark as ERRORS all that accesses of undefined global variables, duplicated parameters / propert

Those of us who work a lot with JavaScript often face a small issue with Autocompletion which turns to be not a small issue but a big mess. By default, completion works for all JavaScript files located under your project root. This may lead to a long and almost unusable completion list. Even if you use just a few JavaScript libraries in your project like jQuery, Ext JS and MooFX, you can get up to 4,000 autocompletion hints for Document object coming from all those libraries! And even when you type e.g. “set”, you'll still end up with about 200 functions starting with “set” . Not a lot of he

Recently, we've added a number of new features that simplify HTML5 development. Here's a short list of their highlights: Support of HTML custom data attributes. The attributes with names that begin with data- can be used to store some custom information. WebStorm/PhpStorm IDE provides completion for such attributes when they're used in a project: Support for Web SQL Database JavaScript API: We also added a new setting Default HTML language level ( File | Settings | Resources ). If you switch it to HTML5, IDE will consider every *.html file without specified doctype as HTML5 file, so vali