WebStorm 11 EAP, 143.88: bug fixes
A new WebStorm 11 EAP build (143.88) is now available for download.
This build addresses the issues with templates strings and unresolved paths in JavaScript that were found in the previous EAP build.
The full list of fixed issues is available in the release notes. You can use a patch update from the previous EAP build (142.5255).
Please report your feedback to our issue tracker. To get notifications of new EAP builds as they become available, subscribe to the EAP channel in Preferences | Appearance & Behavior | System Settings | Updates.
Read about features and improvements added in WebStorm 11:
- WebStorm 11 Early Access Program: Improved TypeScript 1.5 support, TSLint integration, Yeoman integration, new Node.js inspections, support for debugging Webpack, option to run single Mocha test, flame charts in V8 CPU profiler and more.
- WebStorm 11 EAP, 142.3805: Improved HiDPI support for Windows and Linux, clickable links in comments, breadcrumbs in Stylus files.
- WebStorm 11 EAP, 142.4148: Encode HTML symbols, Meteor, TypeScript 1.6 features.
- WebStorm 11 EAP, 142.4723: New formatting options for chained methods, React and TypeScript 1.6 support improvements.
- WebStorm 11 EAP, 142.5255: Flow support, npm scripts, JSX in TypeScript.
Develop with pleasure!
– JetBrains WebStorm Team
Andres says:
October 6, 2015Any ETA on when not being able to debug into node_modules will be fixed? Issue is here – https://youtrack.jetbrains.com/issue/WEB-18160
Ekaterina Prigara says:
October 7, 2015Asked our colleague too have a look, hope he’ll fix that soon.
Andres says:
October 7, 2015Thank you and tell your colleague thank you as well! This issue pretty much is preventing me to jump to Webstorm 11.
jiverson says:
October 7, 2015After the latest build I am unable to commit via git. I get a ‘AssertionError: null’ I am fairly confident it is not because I updated to el capitan. Anyone else having this problem?
Ekaterina Prigara says:
October 7, 2015Can you please report an issue about that on our tracker: https://youtrack.jetbrains.com/issues/IDEA We need a bit more details and a stack trace from the error, so it would be much easier to communicate via the issue. Thank you!
Nils Hartmann says:
October 7, 2015I have the same problem and created an issue:
https://youtrack.jetbrains.com/issue/IDEA-146136
Ekaterina Prigara says:
October 8, 2015Thanks! The fix will be available in the next EAP build.
robert says:
October 8, 2015I installed the new WebStorm-EAP-143.88-custom-jdk-bundled.dmg
It set the left project panel font size much larger and not clear anymore. When I try to change the font style from preference -> editor -> color & fonts it only change the style in the right editor part.
I can not find a way to change the font size of that awesome left project navigation panel. So i put this dam upgrade to Trash then donwload the stabled 10.0.4.
Is there a way for us to change the font size of left project panel back to (DEFAULT)?
Ekaterina Prigara says:
October 9, 2015Can you please send us a screenshot? That’s unknown issue and we need a bit more details. Thank you!
robert says:
October 12, 2015I have opened a issue here : https://youtrack.jetbrains.com/issue/WEB-18538
Sorry, about the previous angry post. I just want someone can point me how I can change the font in the project panel back to Webstorm 10.
Matt Revell says:
October 13, 2015Getting a lot of “attribute is not allowed here” in my jsx files when putting props on my elements – this is within flow and jsx harmony modes.
Ekaterina Prigara says:
October 19, 2015At the moment WebStorm needs react library files in the project to get the list of react-specific attributes, we’re thinking about the ways we can improve the set up.
Mark Shust says:
November 3, 2015Is there any progress on the React lib files yet? I’m also getting a lot of ‘attribute is not allowed here’. It’s very hard to inspect my files right now with React & WebStorm.
Ekaterina Prigara says:
November 3, 2015Replied to you on Twitter.
Doron Zavelevsky says:
March 31, 2016Can you reply here too? thanks.
Ekaterina Prigara says:
March 31, 2016Don’t know what my answer on Twitter was back in November 🙂 But to have JSX tag attributes resolved you need to have react library files in the projects or react.d.ts configured as a JavaScript library via Preferences | Languages and Frameworks | JavaScript | Libraries – Download – search for react.