Cannot find module '@angular-devkit/core'
up vote
45
down vote
favorite
I have created a angular project with Angular CLI: 1.6.3 Node: 9.4.0
OS: linux x64 version. But when want to run my angular app with command ng serve then fetch this error
Cannot find module '@angular-devkit/core'.
javascript angular ecmascript-6 angular-cli
add a comment |
up vote
45
down vote
favorite
I have created a angular project with Angular CLI: 1.6.3 Node: 9.4.0
OS: linux x64 version. But when want to run my angular app with command ng serve then fetch this error
Cannot find module '@angular-devkit/core'.
javascript angular ecmascript-6 angular-cli
please mark the answer
– Sajeetharan
Apr 8 at 16:22
add a comment |
up vote
45
down vote
favorite
up vote
45
down vote
favorite
I have created a angular project with Angular CLI: 1.6.3 Node: 9.4.0
OS: linux x64 version. But when want to run my angular app with command ng serve then fetch this error
Cannot find module '@angular-devkit/core'.
javascript angular ecmascript-6 angular-cli
I have created a angular project with Angular CLI: 1.6.3 Node: 9.4.0
OS: linux x64 version. But when want to run my angular app with command ng serve then fetch this error
Cannot find module '@angular-devkit/core'.
javascript angular ecmascript-6 angular-cli
javascript angular ecmascript-6 angular-cli
edited Nov 22 at 8:14
לבני מלכה
8,1461524
8,1461524
asked Jan 23 at 4:01
azmul hossain
368139
368139
please mark the answer
– Sajeetharan
Apr 8 at 16:22
add a comment |
please mark the answer
– Sajeetharan
Apr 8 at 16:22
please mark the answer
– Sajeetharan
Apr 8 at 16:22
please mark the answer
– Sajeetharan
Apr 8 at 16:22
add a comment |
10 Answers
10
active
oldest
votes
up vote
70
down vote
Try the following steps,
Step 1:
npm update -g @angular/cli
Step 2:
Edit your package.json changing the line
"@angular/cli": "1.6.0",
to
"@angular/cli": "^1.6.0"
,
STEP 3:
npm update
Refer the steps
3
This helped me, +1 for that. But could you also add information on what these are solving?
– Aragorn
Jan 26 at 15:27
This was it. Solved the problem
– Prabo
Feb 16 at 12:58
I had to clear out node_modules, and do a fresh install using npm install, after updating the version to "^1.6.0".
– Sudhir
Mar 8 at 14:01
I would give +1 if there'd be any explanation as to the cause of this. Freaking ridiculous to get compilation error on a fresh new project...
– Mateusz Migała
Mar 15 at 17:19
im not sure what explanation to provide! the commands are self explanatory and it was a bug which is fixed afaik
– Sajeetharan
Mar 15 at 17:24
add a comment |
up vote
20
down vote
Step1: Edit your package.json changing the line
@angular/cli": "1.6.4"
to
@angular/cli": "^1.6.4"
Step2:
npm update -g @angular/cli
Step3:
npm install --save-dev @angular/cli@latest
I was facing the exact same problem. These three did the tasks for me. You may like to see https://github.com/angular/angular-cli/issues/9307
1
I used "npm update -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest", after that, the error disappear
– IcyBrk
Jan 27 at 16:23
Sorry, mistakes made, the command I actually used was "npm install -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest"
– IcyBrk
Jan 27 at 19:20
add a comment |
up vote
14
down vote
try this out
npm install @angular-devkit/core --save-dev
https://github.com/angular/devkit/issues/256
try to update your angular cli
https://github.com/angular/angular-cli/issues/9307
add a comment |
up vote
8
down vote
This can happen on different versions on angular-cli.
You can install it manually with
npm i -D @angular-devkit/core
-D is shortcut to --save-dev
Or try the latest version of angular cli
npm install --save-dev @angular/cli@latest
1
This combined with running npm install again, worked for me!
– onmyway
Jan 23 at 5:18
add a comment |
up vote
1
down vote
package.json, change to "@angular/cli": "^1.6.5",
"devDependencies": {
"@angular/cli": "^1.6.5",
"@angular/compiler-cli": "^5.0.0",
Important, the version could be vary depends on what time.
You really should run
npm update -g @angular/cli
first, to get version, my is 1.6.5
What does the "^" do?
~1.0.2 means to install version 1.0.2 or the latest patch version such as 1.0.4.
^1.0.2 means to install version 1.0.2 or the latest minor or patch version such as 1.1.0.
last, run this
npm update
add a comment |
up vote
1
down vote
Just run:
npm install --save-dev @angular/cli@latest
In the project folder, to fix it.
add a comment |
up vote
0
down vote
You can do
First,
Delete the node_modules
folder
Run npm install
And add devkit to your dev dependancies with npm i -D @angular-devkit/core
add a comment |
up vote
0
down vote
Step 1: delete package-lock.json
Step 2: npm update -g @angular/cli
Step 3: update @angular/cli new version in package.json
Step 4: npm install
It worked for me.
add a comment |
up vote
0
down vote
I only installed my angular/cli using:npm install -g @angular/cli@1.5.2
And I started getting this error.
Solution:
If your version is global and
If you don't mind the version of your angular/cli then type:npm update -g @angular/cli
add a comment |
up vote
0
down vote
This is what worked for me,
Go to the folder where you have the project from command line.
run the command:
npm install @angular-devkit/core
If you see the above image, I found some vulnerabilities which needed to fixed.
run the following commands in sequence:
Step 1: npm audit fix
Step 2: npm install
add a comment |
10 Answers
10
active
oldest
votes
10 Answers
10
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
70
down vote
Try the following steps,
Step 1:
npm update -g @angular/cli
Step 2:
Edit your package.json changing the line
"@angular/cli": "1.6.0",
to
"@angular/cli": "^1.6.0"
,
STEP 3:
npm update
Refer the steps
3
This helped me, +1 for that. But could you also add information on what these are solving?
– Aragorn
Jan 26 at 15:27
This was it. Solved the problem
– Prabo
Feb 16 at 12:58
I had to clear out node_modules, and do a fresh install using npm install, after updating the version to "^1.6.0".
– Sudhir
Mar 8 at 14:01
I would give +1 if there'd be any explanation as to the cause of this. Freaking ridiculous to get compilation error on a fresh new project...
– Mateusz Migała
Mar 15 at 17:19
im not sure what explanation to provide! the commands are self explanatory and it was a bug which is fixed afaik
– Sajeetharan
Mar 15 at 17:24
add a comment |
up vote
70
down vote
Try the following steps,
Step 1:
npm update -g @angular/cli
Step 2:
Edit your package.json changing the line
"@angular/cli": "1.6.0",
to
"@angular/cli": "^1.6.0"
,
STEP 3:
npm update
Refer the steps
3
This helped me, +1 for that. But could you also add information on what these are solving?
– Aragorn
Jan 26 at 15:27
This was it. Solved the problem
– Prabo
Feb 16 at 12:58
I had to clear out node_modules, and do a fresh install using npm install, after updating the version to "^1.6.0".
– Sudhir
Mar 8 at 14:01
I would give +1 if there'd be any explanation as to the cause of this. Freaking ridiculous to get compilation error on a fresh new project...
– Mateusz Migała
Mar 15 at 17:19
im not sure what explanation to provide! the commands are self explanatory and it was a bug which is fixed afaik
– Sajeetharan
Mar 15 at 17:24
add a comment |
up vote
70
down vote
up vote
70
down vote
Try the following steps,
Step 1:
npm update -g @angular/cli
Step 2:
Edit your package.json changing the line
"@angular/cli": "1.6.0",
to
"@angular/cli": "^1.6.0"
,
STEP 3:
npm update
Refer the steps
Try the following steps,
Step 1:
npm update -g @angular/cli
Step 2:
Edit your package.json changing the line
"@angular/cli": "1.6.0",
to
"@angular/cli": "^1.6.0"
,
STEP 3:
npm update
Refer the steps
edited Jun 22 at 4:09
Shashank Vivek
3,97232254
3,97232254
answered Jan 23 at 4:02
Sajeetharan
115k27157215
115k27157215
3
This helped me, +1 for that. But could you also add information on what these are solving?
– Aragorn
Jan 26 at 15:27
This was it. Solved the problem
– Prabo
Feb 16 at 12:58
I had to clear out node_modules, and do a fresh install using npm install, after updating the version to "^1.6.0".
– Sudhir
Mar 8 at 14:01
I would give +1 if there'd be any explanation as to the cause of this. Freaking ridiculous to get compilation error on a fresh new project...
– Mateusz Migała
Mar 15 at 17:19
im not sure what explanation to provide! the commands are self explanatory and it was a bug which is fixed afaik
– Sajeetharan
Mar 15 at 17:24
add a comment |
3
This helped me, +1 for that. But could you also add information on what these are solving?
– Aragorn
Jan 26 at 15:27
This was it. Solved the problem
– Prabo
Feb 16 at 12:58
I had to clear out node_modules, and do a fresh install using npm install, after updating the version to "^1.6.0".
– Sudhir
Mar 8 at 14:01
I would give +1 if there'd be any explanation as to the cause of this. Freaking ridiculous to get compilation error on a fresh new project...
– Mateusz Migała
Mar 15 at 17:19
im not sure what explanation to provide! the commands are self explanatory and it was a bug which is fixed afaik
– Sajeetharan
Mar 15 at 17:24
3
3
This helped me, +1 for that. But could you also add information on what these are solving?
– Aragorn
Jan 26 at 15:27
This helped me, +1 for that. But could you also add information on what these are solving?
– Aragorn
Jan 26 at 15:27
This was it. Solved the problem
– Prabo
Feb 16 at 12:58
This was it. Solved the problem
– Prabo
Feb 16 at 12:58
I had to clear out node_modules, and do a fresh install using npm install, after updating the version to "^1.6.0".
– Sudhir
Mar 8 at 14:01
I had to clear out node_modules, and do a fresh install using npm install, after updating the version to "^1.6.0".
– Sudhir
Mar 8 at 14:01
I would give +1 if there'd be any explanation as to the cause of this. Freaking ridiculous to get compilation error on a fresh new project...
– Mateusz Migała
Mar 15 at 17:19
I would give +1 if there'd be any explanation as to the cause of this. Freaking ridiculous to get compilation error on a fresh new project...
– Mateusz Migała
Mar 15 at 17:19
im not sure what explanation to provide! the commands are self explanatory and it was a bug which is fixed afaik
– Sajeetharan
Mar 15 at 17:24
im not sure what explanation to provide! the commands are self explanatory and it was a bug which is fixed afaik
– Sajeetharan
Mar 15 at 17:24
add a comment |
up vote
20
down vote
Step1: Edit your package.json changing the line
@angular/cli": "1.6.4"
to
@angular/cli": "^1.6.4"
Step2:
npm update -g @angular/cli
Step3:
npm install --save-dev @angular/cli@latest
I was facing the exact same problem. These three did the tasks for me. You may like to see https://github.com/angular/angular-cli/issues/9307
1
I used "npm update -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest", after that, the error disappear
– IcyBrk
Jan 27 at 16:23
Sorry, mistakes made, the command I actually used was "npm install -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest"
– IcyBrk
Jan 27 at 19:20
add a comment |
up vote
20
down vote
Step1: Edit your package.json changing the line
@angular/cli": "1.6.4"
to
@angular/cli": "^1.6.4"
Step2:
npm update -g @angular/cli
Step3:
npm install --save-dev @angular/cli@latest
I was facing the exact same problem. These three did the tasks for me. You may like to see https://github.com/angular/angular-cli/issues/9307
1
I used "npm update -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest", after that, the error disappear
– IcyBrk
Jan 27 at 16:23
Sorry, mistakes made, the command I actually used was "npm install -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest"
– IcyBrk
Jan 27 at 19:20
add a comment |
up vote
20
down vote
up vote
20
down vote
Step1: Edit your package.json changing the line
@angular/cli": "1.6.4"
to
@angular/cli": "^1.6.4"
Step2:
npm update -g @angular/cli
Step3:
npm install --save-dev @angular/cli@latest
I was facing the exact same problem. These three did the tasks for me. You may like to see https://github.com/angular/angular-cli/issues/9307
Step1: Edit your package.json changing the line
@angular/cli": "1.6.4"
to
@angular/cli": "^1.6.4"
Step2:
npm update -g @angular/cli
Step3:
npm install --save-dev @angular/cli@latest
I was facing the exact same problem. These three did the tasks for me. You may like to see https://github.com/angular/angular-cli/issues/9307
edited Jan 23 at 7:08
Pieter
8741120
8741120
answered Jan 23 at 6:42
krishna murari
2256
2256
1
I used "npm update -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest", after that, the error disappear
– IcyBrk
Jan 27 at 16:23
Sorry, mistakes made, the command I actually used was "npm install -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest"
– IcyBrk
Jan 27 at 19:20
add a comment |
1
I used "npm update -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest", after that, the error disappear
– IcyBrk
Jan 27 at 16:23
Sorry, mistakes made, the command I actually used was "npm install -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest"
– IcyBrk
Jan 27 at 19:20
1
1
I used "npm update -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest", after that, the error disappear
– IcyBrk
Jan 27 at 16:23
I used "npm update -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest", after that, the error disappear
– IcyBrk
Jan 27 at 16:23
Sorry, mistakes made, the command I actually used was "npm install -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest"
– IcyBrk
Jan 27 at 19:20
Sorry, mistakes made, the command I actually used was "npm install -g @angular/cli@latest" then "npm install --save-dev @angular/cli@latest"
– IcyBrk
Jan 27 at 19:20
add a comment |
up vote
14
down vote
try this out
npm install @angular-devkit/core --save-dev
https://github.com/angular/devkit/issues/256
try to update your angular cli
https://github.com/angular/angular-cli/issues/9307
add a comment |
up vote
14
down vote
try this out
npm install @angular-devkit/core --save-dev
https://github.com/angular/devkit/issues/256
try to update your angular cli
https://github.com/angular/angular-cli/issues/9307
add a comment |
up vote
14
down vote
up vote
14
down vote
try this out
npm install @angular-devkit/core --save-dev
https://github.com/angular/devkit/issues/256
try to update your angular cli
https://github.com/angular/angular-cli/issues/9307
try this out
npm install @angular-devkit/core --save-dev
https://github.com/angular/devkit/issues/256
try to update your angular cli
https://github.com/angular/angular-cli/issues/9307
answered Jan 25 at 18:06
inyee
1629
1629
add a comment |
add a comment |
up vote
8
down vote
This can happen on different versions on angular-cli.
You can install it manually with
npm i -D @angular-devkit/core
-D is shortcut to --save-dev
Or try the latest version of angular cli
npm install --save-dev @angular/cli@latest
1
This combined with running npm install again, worked for me!
– onmyway
Jan 23 at 5:18
add a comment |
up vote
8
down vote
This can happen on different versions on angular-cli.
You can install it manually with
npm i -D @angular-devkit/core
-D is shortcut to --save-dev
Or try the latest version of angular cli
npm install --save-dev @angular/cli@latest
1
This combined with running npm install again, worked for me!
– onmyway
Jan 23 at 5:18
add a comment |
up vote
8
down vote
up vote
8
down vote
This can happen on different versions on angular-cli.
You can install it manually with
npm i -D @angular-devkit/core
-D is shortcut to --save-dev
Or try the latest version of angular cli
npm install --save-dev @angular/cli@latest
This can happen on different versions on angular-cli.
You can install it manually with
npm i -D @angular-devkit/core
-D is shortcut to --save-dev
Or try the latest version of angular cli
npm install --save-dev @angular/cli@latest
edited May 15 at 9:57
answered Jan 23 at 4:01
alexKhymenko
3,012725
3,012725
1
This combined with running npm install again, worked for me!
– onmyway
Jan 23 at 5:18
add a comment |
1
This combined with running npm install again, worked for me!
– onmyway
Jan 23 at 5:18
1
1
This combined with running npm install again, worked for me!
– onmyway
Jan 23 at 5:18
This combined with running npm install again, worked for me!
– onmyway
Jan 23 at 5:18
add a comment |
up vote
1
down vote
package.json, change to "@angular/cli": "^1.6.5",
"devDependencies": {
"@angular/cli": "^1.6.5",
"@angular/compiler-cli": "^5.0.0",
Important, the version could be vary depends on what time.
You really should run
npm update -g @angular/cli
first, to get version, my is 1.6.5
What does the "^" do?
~1.0.2 means to install version 1.0.2 or the latest patch version such as 1.0.4.
^1.0.2 means to install version 1.0.2 or the latest minor or patch version such as 1.1.0.
last, run this
npm update
add a comment |
up vote
1
down vote
package.json, change to "@angular/cli": "^1.6.5",
"devDependencies": {
"@angular/cli": "^1.6.5",
"@angular/compiler-cli": "^5.0.0",
Important, the version could be vary depends on what time.
You really should run
npm update -g @angular/cli
first, to get version, my is 1.6.5
What does the "^" do?
~1.0.2 means to install version 1.0.2 or the latest patch version such as 1.0.4.
^1.0.2 means to install version 1.0.2 or the latest minor or patch version such as 1.1.0.
last, run this
npm update
add a comment |
up vote
1
down vote
up vote
1
down vote
package.json, change to "@angular/cli": "^1.6.5",
"devDependencies": {
"@angular/cli": "^1.6.5",
"@angular/compiler-cli": "^5.0.0",
Important, the version could be vary depends on what time.
You really should run
npm update -g @angular/cli
first, to get version, my is 1.6.5
What does the "^" do?
~1.0.2 means to install version 1.0.2 or the latest patch version such as 1.0.4.
^1.0.2 means to install version 1.0.2 or the latest minor or patch version such as 1.1.0.
last, run this
npm update
package.json, change to "@angular/cli": "^1.6.5",
"devDependencies": {
"@angular/cli": "^1.6.5",
"@angular/compiler-cli": "^5.0.0",
Important, the version could be vary depends on what time.
You really should run
npm update -g @angular/cli
first, to get version, my is 1.6.5
What does the "^" do?
~1.0.2 means to install version 1.0.2 or the latest patch version such as 1.0.4.
^1.0.2 means to install version 1.0.2 or the latest minor or patch version such as 1.1.0.
last, run this
npm update
edited Jan 23 at 17:29
answered Jan 23 at 17:24
hoogw
1,1211213
1,1211213
add a comment |
add a comment |
up vote
1
down vote
Just run:
npm install --save-dev @angular/cli@latest
In the project folder, to fix it.
add a comment |
up vote
1
down vote
Just run:
npm install --save-dev @angular/cli@latest
In the project folder, to fix it.
add a comment |
up vote
1
down vote
up vote
1
down vote
Just run:
npm install --save-dev @angular/cli@latest
In the project folder, to fix it.
Just run:
npm install --save-dev @angular/cli@latest
In the project folder, to fix it.
edited Apr 14 at 1:33
Stephen Rauch
27.4k153156
27.4k153156
answered Apr 14 at 1:12
JMck
111
111
add a comment |
add a comment |
up vote
0
down vote
You can do
First,
Delete the node_modules
folder
Run npm install
And add devkit to your dev dependancies with npm i -D @angular-devkit/core
add a comment |
up vote
0
down vote
You can do
First,
Delete the node_modules
folder
Run npm install
And add devkit to your dev dependancies with npm i -D @angular-devkit/core
add a comment |
up vote
0
down vote
up vote
0
down vote
You can do
First,
Delete the node_modules
folder
Run npm install
And add devkit to your dev dependancies with npm i -D @angular-devkit/core
You can do
First,
Delete the node_modules
folder
Run npm install
And add devkit to your dev dependancies with npm i -D @angular-devkit/core
answered Jan 24 at 13:19
tolotrasmile
515
515
add a comment |
add a comment |
up vote
0
down vote
Step 1: delete package-lock.json
Step 2: npm update -g @angular/cli
Step 3: update @angular/cli new version in package.json
Step 4: npm install
It worked for me.
add a comment |
up vote
0
down vote
Step 1: delete package-lock.json
Step 2: npm update -g @angular/cli
Step 3: update @angular/cli new version in package.json
Step 4: npm install
It worked for me.
add a comment |
up vote
0
down vote
up vote
0
down vote
Step 1: delete package-lock.json
Step 2: npm update -g @angular/cli
Step 3: update @angular/cli new version in package.json
Step 4: npm install
It worked for me.
Step 1: delete package-lock.json
Step 2: npm update -g @angular/cli
Step 3: update @angular/cli new version in package.json
Step 4: npm install
It worked for me.
answered Feb 13 at 12:08
Arvind Mehta
94
94
add a comment |
add a comment |
up vote
0
down vote
I only installed my angular/cli using:npm install -g @angular/cli@1.5.2
And I started getting this error.
Solution:
If your version is global and
If you don't mind the version of your angular/cli then type:npm update -g @angular/cli
add a comment |
up vote
0
down vote
I only installed my angular/cli using:npm install -g @angular/cli@1.5.2
And I started getting this error.
Solution:
If your version is global and
If you don't mind the version of your angular/cli then type:npm update -g @angular/cli
add a comment |
up vote
0
down vote
up vote
0
down vote
I only installed my angular/cli using:npm install -g @angular/cli@1.5.2
And I started getting this error.
Solution:
If your version is global and
If you don't mind the version of your angular/cli then type:npm update -g @angular/cli
I only installed my angular/cli using:npm install -g @angular/cli@1.5.2
And I started getting this error.
Solution:
If your version is global and
If you don't mind the version of your angular/cli then type:npm update -g @angular/cli
answered Feb 16 at 0:48
danilo
4332819
4332819
add a comment |
add a comment |
up vote
0
down vote
This is what worked for me,
Go to the folder where you have the project from command line.
run the command:
npm install @angular-devkit/core
If you see the above image, I found some vulnerabilities which needed to fixed.
run the following commands in sequence:
Step 1: npm audit fix
Step 2: npm install
add a comment |
up vote
0
down vote
This is what worked for me,
Go to the folder where you have the project from command line.
run the command:
npm install @angular-devkit/core
If you see the above image, I found some vulnerabilities which needed to fixed.
run the following commands in sequence:
Step 1: npm audit fix
Step 2: npm install
add a comment |
up vote
0
down vote
up vote
0
down vote
This is what worked for me,
Go to the folder where you have the project from command line.
run the command:
npm install @angular-devkit/core
If you see the above image, I found some vulnerabilities which needed to fixed.
run the following commands in sequence:
Step 1: npm audit fix
Step 2: npm install
This is what worked for me,
Go to the folder where you have the project from command line.
run the command:
npm install @angular-devkit/core
If you see the above image, I found some vulnerabilities which needed to fixed.
run the following commands in sequence:
Step 1: npm audit fix
Step 2: npm install
answered Sep 28 at 17:01
Vineela Thonupunuri
4010
4010
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48394003%2fcannot-find-module-angular-devkit-core%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
please mark the answer
– Sajeetharan
Apr 8 at 16:22