Debugging angular-cli in WebStorm
Related questions
Debugging angular-cli in WebStorm
imported from
Using angular-cli starting project with WebStorm (PhpStorm).
I want to use debug - it seems to work but except it isn't :/
Here are some screen shots.
Here is mine first breakpoint
Next breakpoint
And my settings
See also questions close to this topic
Our Java application is going through migration from a WAS 7 server to a WAS 8.5 server - and for some reason, even though our application shows as Deployed in our Admin Console, the application itself isn't coming up on our assigned URL.
I've ruled out the possibility of a code-related problem by testing the application in my local server, so I know the problem is with some server settings - but, almost all of my experience in CS is in coding, and I don't know how to figure out where those settings have gone awry.
What options do I have to debug my application's server-side issues?
When I'm in the debugging perspective my first AJAX call is done within under 1s. If I execute the same code without debugging, the first call takes up 1min whereas the subsequent calls are under 1s again.
(reproduced Chrome, Firefox and IE)
My AJAX call:
var getJSONfromURL = function(url, callback){
//removed '.ready' according to @adeneo's and @Jeremy_Thille's comments
//$(document).ready(function(){
var request = $.getJSON(url, callback);
request.done(function(){
//something...
Further Details
The HTML-document that calls this function takes about 200ms to load.
The callback-function and the request.done part are executed ~1min after getJSONFromURL finishes.
A console.log() showed that the getJSON is being called once.
The same behaviour is being observed when I use XMLHttpRequests. (The ReadyState changes after ~1min.)
Loading the URL in the Browser takes under 1s.
The size of the JSON to be loaded is about 500B.
Both the HTML executing the call and the JSON being requested are on localhost. (The latter is from a MongoDB-NOSQL database REST-API.)
Concerning JS surrounding this function: This script is being called right after the loading of the HTML. The only time consuming operations that happen before it are the loading of google.charts and jquery.
No graphics are being loaded on the page.
Conclusion
Why do I have this discrepancy between the loading times in the two different perspectives?
Why does it only happen with the first AJAX call?
What can I do to speed up the process?
How can I observe what's taking so long without using the debugger?
Thank you in advance for any help, ideas, explanations,...
I had the below output (along with monkey with a hammer picture at the right)
when I tried opening youtube on chromium. I was wondering how the lengthy output aids google engineers in debugging rather than a screenshot.
Sorry, something went wrong.
A team of highly trained monkeys has been dispatched to deal with this
situation.
If you see them, send them this information as text (screenshots
frighten them):
APCGX7qycD8BRvqozjCuAupL2ggiqnNJ1EsrpiaYPzWXju4RMoCg7Npp
AJqjgxc7PGoiyYTEmoJGn2JVvEbyAVDPMvvqGi1GF4DtQX-86Vky3FfR
CH-eUDuTpaa9Jrlk16e2-OOOfEZ3i4wMFb3skJdRtBGPh9nMlnq3UbL1
DCxj8wGM4JyUzWhi8gxbJeshXkuTeHwWtZ0iVKwV1YohiQlMLuNgIqzw
J73G-dI0G2vOBMvQGCyQgEUUVUOOpmv4XphggiLg1USeyJ-28GurSbqd
2C9a3nitWqfzUYwnBmEaHCE-rnuYOr6qplmTBFrUZOWl7vB0204fxuvR
PX0WWFgz__GFVzGVhUKnn57nyAOuUsPN6z9rHz6QPPUwdJ566jQcbxQC
bmjVhb86wjfatpKSdjKT8jhk_P6SBEbpwJeNS2udXG2he55GRwM-3P6-
JjNAU0Ayh0buv_h-QV6zQ8DiYpmp0Lkx-1JZtT-P5Nwrje8V_viOU4K3
bl_ixYW7Be2O_IsskWP2YtvXHmhJaOb451Zswzh2izjDcqrVUO-LsxZk
DgIgSRcDsPLurn-6f6bsl_mQ6Y1JvZGIo5pvWiNdyogCfEGrAVSq-jEb
TrrKY8LJpVaRgJ8Idx2QUZDt6CZ-c-2qScEVQHvUpoA9SPNmytBunFUE
eS9NR1HbSH_Q1nzZWXnvuIWN-IQ25zAW0Awfq0-GAoFeZGpa8fHiLMwU
lTyWettPjJbbdJmsn8u9_Qit7CIaCZ1QiMNk_aBJagrj4Bwhe-ghLsqh
n8Hod9P6nrYQvSBegqcFXXOfsUaV1-Ue4KhibkhwNhse-N3K7p_5e4jn
7DGdORpAri_9XIXeC6lIAo7ZnweijyPqXIRGxCgunJCxVvALmIx8t6me
Y-YW7ww7066U-CocEzK9GFmD5URqPPE86ajiKbSIbS3rEfIpAPc7VNjW
xoL_VUnznBA6TmSreQRJso2JQTni0DixVKCnFxafjGLn2GKYAI6VSvjn
K_lfujqSS9HNeotAfucJWgzh5P4X46DfyxZ6GusP20MPM3s8G1qh1ZqV
YMh-Ae7f3veMT1TGxkr0vDwewb1OQgdHb4VSCAaRA-0TRGGdjtX-_1Mn
K6lA6j1IDnDR-MgToqss4T5DPMsom8GKVdnDCgAYVI3CHQKg2zFSriC8
ZRi-G4laQpCaRAP10JVfD7eha0Xn6dn_m_XCGRafttgHgWYw9CGiA4yt
Z4xEjmcohEPL7Ie_OfbG9Tz15HWGtXIZQSc9RujtVwwo8NhX3HEhl5pe
3pyQW3gOAYaZF6b2RuXugLXSheI4L7ZhkI_bf458oN4iO6LS-LdTSTYB
XyR_4PBSG0qrmWPUiuMPk_qOtJNjGY1kqVdfwS0Z9dfWWtnDo38AjQoa
B4irGjp6aG321cXvI3HuE9v7nt7tVW2psig4h9g6HN5e4Q7v9YWtdIQZ
j4_MRXlMXcIqdNM9i9khQHxZZLM73xwNIMENwqhi7UT1EqT19onkVAFV
y96eIJspImmOprJuVoA2OZ2UsjVGYrSXHZTHCFywKPzy2vU0TiGVk6G6
kjib1PcIKDagEXN-a9y_0YllxaYByZ5wWNK6XCBSm6Ys7a3Cbj6cUsTo
bAyLouN0lkKqAq_WqGSHWqU-7ncUi7yflz7tzKh9U5IFajcn8I5j74eS
KbNzyQpPh7eAXBMoyn6zXJN7rf8C3dP1HIwBbC42ZYNCKnv8sKBR86IA
1k6Y1bKM9fcCBGwADnME3dGwsZpum3AtvLx_i6OP8VglOZjb-BcAQQAl
icbDkJTAbd8clRjFpkqKiScQuzMdTZFkVf6NC6WSAJ1M6kLU2mCOSGp6
nASyAj7jKDh6xtgCDF_NWLh_KfCR_v1y-pVIepn3_50bbyNkbuAoN8z2
GKXAOZG9ZRFHpQ7V2FFbt8HrXXoCYnVDidbFoRRdnPiUaDzMOwBYc1qW
4ArjAYg-2Np_H_fJapb-75w--mnGQRldLnPJQ2TiutCozjQnqRm8PIZ0
eAALVq_z1AtE5qOsAkROSMEGiKcpKxF7G72PPgti511LPlYvZ4K6dAYK
mpMPFZZKrWyehgOa7PvHX-hzWXK1ds-DDxugkfKVImDUWCqyIUbkdeRc
kQJShl3eGc8cc4tyOIR9hrkeuHpiGiCocV9yusI4iEMmc-0mt-17ihsM
0l-xuxhtx_V4d_pdHuAwQwloQwVg-KL39jW9Et_y2NKtkgXZIjaUdoW8
I8WvATN1q-F_RMVoiMubX_-V18IlMGl98fd9MPB6oeSp6zZ_LGy5hwsZ
UuWy0FKmpssebG3OcaxDVz93hnlSN0DpQ7Wd1flD6dVEi_eacHF1VqSf
DoRHSQvPqLaHjsuN6EMUT_2z-Fj6BNTKWEN1PFjPxUCoqcN5LjDYM332
okB-ufNwjzagWZieRHLmhi57kjCpPGerWjN0PCeyxpQkiaDAG15Zgu1_
5_O0p7jbpwh4sEuvVlwxdaFnDWxzmjFZr8ntT1PTEDylqO72Goft74w7
ZnPbm48TPyQebHAqrZcamDor16KJqQTDXKYmwxgy-VDFDp2_uml-sK68
6zTMRNnU1XEQtkYnT8JrDBocI8OJgcQti7iXpJu6XkgRRrUdyyhY6KMO
zTaOCDazYlkX38U0FccBuR99MXzD9iXOp6hf_MNksHKysv4No3LpomYa
cjsHCrWuB5upVSLHx-e3bULAYxW1ttT_b0RVkqpKYiEyGTtzaacUhvHB
47Ti8LYSwZAB3eggA7DzBTQnu0DU6JZvuMsO-5m2VRsBiEwa8lvUm1Le
DHWnn7NQnjZnfjXgmDeMr-wt1olPm5Es-o2T0f7-Zd5qU3uX9mh0u1nW
0PcNFCY268sWJw_9ehRk7iFnDcbOGEtQMRiBybYQziyK6iaSRj9OYRkC
ZbnP2aYAPApjNh9jeOxX4XEeVa5uusvb3UvThkNt6j0l2YNW4kdZUIxl
L0uZqzZuBXqTH6NX_FL1KkeBe2aMJvRnL5VqvbctZeq-aGAdsnshWEp0
9RAdUIghql9u_eOm8PBBdSH3bPr4ubpfm4za4jztFFuk2iIoewmjOP8I
cBt9Ur8S9Cjna8iNxGYLdnWXAs7Gt2H5WTWpDrefyPRY3GCWOq7_24NH
8AilGTYG9eFlzcMQX4QTyVenqSwujEGJRif0ZxSK6KOd4giubx_EUhL5
-Xwm0eXX46z9cFbJE0flM979iKP5rXQGLncgA8dR9FtbQx5BxJfLMCkv
6rgm_LIo4dPYvOpYyslvWv9e948ejjqfNDXyjdeST5ZXoFyiaOcN5DM_
_kCLquYQXWEYRSW71PrCjI-_OFMkEYRf_EIVJDZCrO6GxDPqGdrHI7u9
Rn4AuD48enhHWZj6mDSnQnEtn91w68gJK9OAIbnBW1FEAFXkuQ8kB1UO
Kc51mz-RgnEgSHf0-me6o_nTadLDPyaWvz00EKutRz8MKGzyngfEkmU2
3VG9sbPX7QsIvUjjbM_pJOl9lnr1L84-Ntbl_EP7kj04MqPCsoFxyogO
M6dLlDt9p3E54J4fJglw2yB9KoK1O4r-QcPicFCzfelQ
I am using the latest version of PhpStorm to build a blog-style site.
For some reason, when opening index.php to view in the browser, running the built-in webserver in PhpStorm, the CSS refuses to load unless the header and footer files are in the root directory of the site. Here's some screens:
Directory structure:
&html lang="en"&
&meta charset="utf-8"&
&meta http-equiv="X-UA-Compatible" content="IE=edge"&
&meta name="viewport" content="width=device-width, initial-scale=1"&
&meta name="description" content="TCT Media"&
&meta name="author" content="TCT Media"&
&title&&?php echo $view-&pageT ?&&/title&
&!-- Bootstrap Core CSS --&
&link href="../../css/bootstrap.min.css" rel="stylesheet" type="text/css"&
&!-- Custom CSS --&
&link href="../../css/1-col-portfolio.css" rel="stylesheet" type="text/css"&
&!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries --&
&!-- WARNING: Respond.js doesn't work if you view the page via file:// --&
&!--[if lt IE 9]&
&script src="/libs/html5shiv/3.7.0/html5shiv.js"&&/script&
&script src="/libs/respond.js/1.4.2/respond.min.js"&&/script&
&![endif]--&
&!-- Navigation --&
&nav class="navbar navbar-inverse navbar-fixed-top" role="navigation"&
&div class="container"&
&!-- Brand and toggle get grouped for better mobile display --&
&div class="navbar-header"&
&button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"&
&span class="sr-only"&Toggle navigation&/span&
&span class="icon-bar"&&/span&
&span class="icon-bar"&&/span&
&span class="icon-bar"&&/span&
&a class="navbar-brand" href="#"&HOME&/a&
&!-- Collect the nav links, forms, and other content for toggling --&
&div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1"&
&ul class="nav navbar-nav"&
&a href="#"&NEWS&/a&
&a href="#"&POLITICS&/a&
&a href="#"&GAMING&/a&
&a href="#"&MUSIC&/a&
&a href="#"&CONTACT US&/a&
&!-- /.navbar-collapse --&
&!-- /.container --&
&!-- Page Content --&
&div class="container"&
&!-- Footer --&
&div class="row"&
&div class="col-lg-12"&
&p&Copyright & TCT Media 2017&/p&
&!-- /.row --&
&!-- /.container --&
&!-- jQuery --&
&script src="../../js/jquery.js"&&/script&
&!-- Bootstrap Core JavaScript --&
&script src="../../js/bootstrap.min.js"&&/script&
index.html:
&?php require_once('template/header.phtml') ?&
&!-- Page Heading --&
&div class="row"&
&div class="col-lg-12"&
&h1 class="page-header"&Craam's Playlist&/h1&
&!-- /.row --&
&iframe width="100%" height="250px" scrolling="no" frameborder="no" src="/player/?url=https%3A///playlists/&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&visual=true"&&/iframe&
&!-- Page Heading --&
&div class="row"&
&div class="col-lg-12"&
&h1 class="page-header"&First Article
&small&What fresh hell is this?&/small&
&!-- /.row --&
&!-- Project One --&
&div class="row"&
&div class="col-md-7"&
&a href="#"&
&img class="img-responsive" src="http://placehold.it/700x300" alt=""&
&div class="col-md-5"&
&h3&Every day we stray further from God&/h3&
&h4&Everyone was harmed during the making of this site&/h4&
&p&Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium veniam exercitationem expedita laborum at voluptate. Labore, voluptates totam at aut nemo deserunt rem magni pariatur quos perspiciatis atque eveniet unde.&/p&
&a class="btn btn-primary" href="#"&View Project &span class="glyphicon glyphicon-chevron-right"&&/span&&/a&
&!-- /.row --&
&!-- Project Two --&
&div class="row"&
&div class="col-md-7"&
&a href="#"&
&img class="img-responsive" src="http://placehold.it/700x300" alt=""&
&div class="col-md-5"&
&h3&Project Two&/h3&
&h4&Subheading&/h4&
&p&Lorem ipsum dolor sit amet, consectetur adipisicing elit. Ut, odit velit cumque vero doloremque repellendus distinctio maiores rem expedita a nam vitae modi quidem similique ducimus! Velit, esse totam tempore.&/p&
&a class="btn btn-primary" href="#"&View Project &span class="glyphicon glyphicon-chevron-right"&&/span&&/a&
&!-- /.row --&
&!-- Project Three --&
&div class="row"&
&div class="col-md-7"&
&a href="#"&
&img class="img-responsive" src="http://placehold.it/700x300" alt=""&
&div class="col-md-5"&
&h3&Project Three&/h3&
&h4&Subheading&/h4&
&p&Lorem ipsum dolor sit amet, consectetur adipisicing elit. Omnis, temporibus, dolores, at, praesentium ut unde repudiandae voluptatum sit ab debitis suscipit fugiat natus velit excepturi amet commodi deleniti alias possimus!&/p&
&a class="btn btn-primary" href="#"&View Project &span class="glyphicon glyphicon-chevron-right"&&/span&&/a&
&!-- /.row --&
&!-- Project Four --&
&div class="row"&
&div class="col-md-7"&
&a href="#"&
&img class="img-responsive" src="http://placehold.it/700x300" alt=""&
&div class="col-md-5"&
&h3&Project Four&/h3&
&h4&Subheading&/h4&
&p&Lorem ipsum dolor sit amet, consectetur adipisicing elit. Explicabo, quidem, consectetur, officia rem officiis illum aliquam perspiciatis aspernatur quod modi hic nemo qui soluta aut eius fugit quam in suscipit?&/p&
&a class="btn btn-primary" href="#"&View Project &span class="glyphicon glyphicon-chevron-right"&&/span&&/a&
&!-- /.row --&
&!-- Project Five --&
&div class="row"&
&div class="col-md-7"&
&a href="#"&
&img class="img-responsive" src="http://placehold.it/700x300" alt=""&
&div class="col-md-5"&
&h3&Project Five&/h3&
&h4&Subheading&/h4&
&p&Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aliquid, quo, minima, inventore voluptatum saepe quos nostrum provident ex quisquam hic odio repellendus atque porro distinctio quae id laboriosam facilis dolorum.&/p&
&a class="btn btn-primary" href="#"&View Project &span class="glyphicon glyphicon-chevron-right"&&/span&&/a&
&!-- /.row --&
&!-- Pagination --&
&div class="row text-center"&
&div class="col-lg-12"&
&ul class="pagination"&
&a href="#"&&&/a&
&li class="active"&
&a href="#"&1&/a&
&a href="#"&2&/a&
&a href="#"&3&/a&
&a href="#"&4&/a&
&a href="#"&5&/a&
&a href="#"&&&/a&
&!-- /.row --&
Anyone have any idea why this is the case? I have built MVC projects in PhpStorm before and not encountered this issue.
The below syntax is working just fine
import Home from '@/pages/Home'
But the following is not: (it throws error about missing of { and from word like above syntax)
In Preferences & Languages & Frameworks & JavaScript I am using the version
ECMAScript 6 (OSX, PhpStorm v)
The compiler works fine but I'd like to remove the file red error alert.
Is there any plugin which supports this syntax on PhpStorm?
I want to sort CodeIgniter's view files by modified date in PhpStorm. I tried but unsuccessful.
Here is a screenshot below:
I've installed nodejs and jasmine-node and it runs in command line.
Configuration of WebStorm Runner:
Node parameters: jasmine-node --config endpoint ServerAddress:8083
Working directory: G:\NPWorkDir\frisby
JavaScript file: src\protocol\find_spec.js
WebStorm Terminal:
"C:\Program Files\JetBrains\WebStorm\bin\runnerw.exe" "G:\Program
Files\nodejs\node.exe" jasmine-node --config endpoint ServerAddress:8083
G:\NPWorkDir\frisby\src\
protocol\find_spec.js
module.js:471
Error: Cannot find module 'G:\NPWorkDir\tester-frisbys\jasmine-node'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
Process finished with exit code 1
I want IntelliJ to reformat code inside of a &style& tag in a React JavaScript(jsx) file. When I reformat code now it just reformats JavaScript parts.
I simply want the code to change from this:
to this automatically:
is it possible?
I'm currently developing angular 2 application. But i'm having a hard time understanding why my routing on works in ng serve and not in nodemon? I've tried out multiple method based on what i've research on but they dont really works like how i thought it would be. (Probably due to my poor understanding)
Adding useHash: true in the app-routing.module.ts But this would cause all the URL to have # appear in it. And i'm thinking this is meant for debugging purposes right?
const routes = [
{ path: '', component: sampleComponent1 },
{ path: 'page2', component: sampleComponent2 }
@NgModule({
imports: [RouterModule.forRoot(routes, {useHash: true})],
exports: [RouterModule]
Change app.js to render index whenever error is thrown. This method would not have # in URL but it will always return error like GET /page2 404 1.688 ms - 987 in my console.
app.use(function (err, req, res, next) {
// set locals, only providing error in development
console.log(err.message);
res.locals.message = err.
res.locals.error = req.app.get('env') === 'development' ? err : {};
res.status(err.status || 500);
res.render('error');
So as of now, I'm sticking more to method 2 as the URL does not show # in it, but i'm not sure if method 2 is the correct way to do it. Can someone help me out on this?
Angular-CLI uses webpack as its module bundler, but I'm confused as to why I don't find a standard webpack config JSON file anywhere in the generated project . . .
How to change webpack.config.js file inside angular/cli project that `ng serve command will not ignore tslint rules.为什么 WebStorm 8 装 AngularJS 插件不成功？ - 知乎5被浏览1609分享邀请回答1添加评论分享收藏感谢收起/webstorm/2014/03/angularjs-workflow-in-webstorm/你得引入才行！ 我的版本9.0.1 1添加评论分享收藏感谢收起1 个回答被折叠（）与世界分享知识、经验和见解用WebStorm进行Angularjs 2开发（环境篇：Windows 10，Angular-cli方式） - 博客频道 - CSDN.NET
洗尽铅华，回归技术本质；繁华落尽，打造本真质量。
我们所耳闻的一切都只是观点而不是事实。我们所看见的都是一个角度而不是真相。——马库斯.奥利利乌斯
分类：nodejsangular
自己学习使用了Angular JS 1一段时间，由于没有具体的项目进行尝试加上其它研究工作的影响，就搁置了一段时间。在与同事讨论技术选型时，才知道Angular JS 2的差别之大（孤陋了，莫见笑），所以决定弄弄Angular 2。WebStorm是进行JS和前端开发的不二之选的IDE工具，虽然目前版本已经更新了，但是由于Angular 2的成熟度还没那么高，所以用WebStorm进行Angular 2的工程创建，还是没有其他语言的方便。自己尝试用WebStorm搭建Angular 2的工程，虽然在网上看了一些仁兄的帖子，很有帮助，但是感觉关键的、核心的问题没有说清楚（也可能是由于用Node不是很久，知识浅薄），所以搭建过程特别是在Windows上也是磕磕绊绊，总是有些问题。相信其他人也会遇到同样的问题，所以将问题梳理总结如下。
既然是使用Angular JS 2，那么先简单说下 1 和 2 的主要区别。这方面内容，网上很多，我就借用其他仁兄的一些资料，具体来源可以查看：参考资料
Angular 1与 Angular 2之间的一些差别
Angular2使用了javascript的超集‘Typescript’，所以angular1和angular2从设定之初就是不一样的；
Angular1.x在设计之初主要是针对pc端的，对移动端支持较少（当然也有其他一些衍生框架如ionic），而Angular2是设计包含移动端的；
Angular 1的核心概念是scope，但是angular2中没有scope，angular2使用zone.js来记录监测变化；
Angular 1 中的控制器在angular2中不再使用，也可以说控制器在angular2中被‘Component’组件所替代：
二、环境准备
Nodejs 7.4.0
angular-cli 0.31
Windows 10 RedStone
WebStorm安装很简单，破解不是本文重点，建议还是支持正版。
（1）Nodejs安装
这一步很简单，下载Windows版的Nodejs，进行按照提示安装即可，记得选择将nodejs增加到PATH一项，如果界面上没有，应该就是默认帮你搞定了，可以忽略我这句废话。
通过命令，验证是否安装成：
如果正常显示版本号，即安装成功。
（2）Nodejs配置
Nodejs安装完成之后，默认会将node.exe的路径，添加到系统的环境变量中，如果没有请手动添加。除此之外还要进行其他的配置。
1、配置prefix和cache目录
示例目录地址为：C:\Program Files\nodejs
npm config set prefix “C:\Program Files\nodejs\node_global”
npm config set cache
“C:\Program Files\nodejs\node_cache
2、配置环境变量
右击“计算机”—&”属性”—&”高级系统设置”—&”环境变量”
在”系统变量”中,设置 NODE_PATH
在系统变量里新建 NODE_PATH ,值为
C:\Program Files\nodejs\node_global\node_modules
这个值就是上一步中，通过 “npm config set prefix” 设置的值。可以，用下面命令查看
npm config get prefix
在”用户变量”中,修改path
修改用户变量中的path，添加C:\Program Files\nodejs\node_global\。
这个值就是上一步中，通过 “npm config set prefix” 设置的值。
3、配置sass_binary
angular cli 是要依赖node-sass的，默认情况下，不会像其它包一样直接下载，而是要下载后进行编译的。在Windows下，首先要通过git下载win32-x64-51_binding.node，但是不知道是被墙还是什么原因，下不下来，就会导致后面的编译出错，以及提示找不到python和Visual Studio的问题。如下：
首先要做的就是根据错误提示，手动下载相应的版本
将下载的binding.node放到指定目录，例如：
C:\win32-x64-51_binding.node
配置路径：通过命令配置
npm config set sass_binary_site “https://npm.taobao.org/mirrors/node-sass/” //使用阿里的镜像
npm config set sass_binary_path
“C:\win32-x64-51_binding.node”
当然以上prefix， cache，sass_binary_site， sass_binary_path等，也可以通过修改下面文件进行配置
C:\&username&\.npmrc
prefix=C:\Program Files\nodejs\node_global
cache=C:\Program Files\nodejs\node_cache
sass_binary_site=https://npm.taobao.org/mirrors/node-sass/
sass_binary_path=C:\win32-x64-51_binding.node
（3）安装工具包
1、全局安装阿里cnpm
npm install -g cnpm --registry=https://registry.npm.taobao.org
2、全局安装typescript
npm install -g typescript typings
3、全局安装angularjs-cli
npm install -g @angular/cli
新版已经不用angular-cli进行安装，而是使用@angular/cli，
三、创建工程
1、打开WebStorm新建一个Angualr CLI 工程
nodejs如果安装好，WebStorm会自己扫描到
指定工程目录和名称
指定angular-cli的目录
很多帖子只说指定angular-cli的目录，没有说清楚具体是哪个目录。但是最开始我在指定的时候，一直还提示“Please specify angular-cli package”。还以为是angualr-cli没有安装对。
通过尝试发现：
（a）具体的目录，就是angular-cli包中，bin目录的上一层目录
（b）如果目录选择完成后，还提示：“Please specify angualr-cli package”，就点击一下工程名称那一栏或其它地方。因为选择angular-cli目录，不会触发事件，所以错误提示一直在，点了其它地方，触发一下事件，提示就会消失，“Create”按钮就可以使用。
2、等待工程创建完成
以上工作完成，就是等待新建一个angular 2工程。这个过程有点慢，主要是IDE会根据package.json下载依赖的包到工程里面。
如果出现上图，就说明工程创建完成，工程结构如下
3、运行程序
选择package.json, 右键选择“Show npm Scripts”，或者用“Edit Configurations”，添加“npm”
点击“start” 启动 Web Server
在浏览器輸入
，若出現 app works! ，表示 Angular 2 已经正常启动。
参考资料：
排名：千里之外
（6）（6）（2）（11）（2）（1）（1）（6）（18）（3）（1）（1）（2）（1）（1）（1）（1）（1）（1）（1）