Problem with npm install

[Sonika2430]

I cannot proceed with npm install. The kind of errors I am getting does not matches to any of the listed cases in the given document. I could not understand the alternative method of copying the node modules in the git repo. I installed git bash for this work. I could not understand which folder I am supposed to open and delete the existing files and then copy the node module files from the link.

[henrypuspurs]

I have the same issue, gonna keep at it see if I can't solve it.

[henrypuspurs]

https://github.com/insidesherpa/JPMC-tech-task-2/issues/293#issuecomment-683364721

This works, its a huge file, there must be a better fix but Id rather get on with the task rather than sit and compare what its changed. you should be able to go straight to starting the client.

[Sonika2430]

#293 (comment)

This works, its a huge file, there must be a better fix but Id rather get on with the task rather than sit and compare what its changed. you should be able to go straight to starting the client.

Thanks a lot for acknowledging and replying. I was on it actually and just started streaming data. Used this method only. Copied the node modules folder manually. Thanx a lot. Cheers!

[Sonika2430]

I started the client. Worked perfectly for sometime when I was making changes to app.tsk and graph.tsk...but after that..the page is not loading at all. tried to run the server afresh. but it says local host 3000 took too long to respond. not able to load the page. Everything in the command line looks perfect though. Any idea???

[henrypuspurs]

I only got that when the server.py ran out of data to send, which happens if you dont stop the client querying for data.

[Kushagratandon12]

Please attach a screenshot of the root folder where you have saved your project then I guess I can help you. before that check, you have a new version of the node installed in your system

[Sonika2430]

I only got that when the server.py ran out of data to send, which happens if you dont stop the client querying for data.

Hey, Thanx for responding! And how do we do that? How to stop client querying for data. Because I do remember that the first time when I was able to see the page, the cmd did show something saying query received successfully or something. But since it stopped working...it never showed the query thing again.

[Sonika2430]

Please attach a screenshot of the root folder where you have saved your project then I guess I can help you. before that check, you have a new version of the node installed in your system

Thanks for responding! I have attached the screenshots.

[henrypuspurs]

I only got that when the server.py ran out of data to send, which happens if you dont stop the client querying for data.

Hey, Thanx for responding! And how do we do that? How to stop client querying for data. Because I do remember that the first time when I was able to see the page, the cmd did show something saying query received successfully or something. But since it stopped working...it never showed the query thing again.

You stop it for the website. The server only sends data on request, so if the client stops asking for it it stops sending. Most foolproof way is to close the browser but refreshing the page works.

[Kushagratandon12]

When node start building its application means when you call (npm install) it creates and downloads some of the files which will be further used for analysis. Now that might be the problem in your case after doing changes in your file, it's better that remove the package-lock file and node_modules folder and then re-run the using npm install. then it might work for you

[Sonika2430]

When node start building its application means when you call (npm install) it creates and downloads some of the files which will be further used for analysis. Now that might be the problem in your case after doing changes in your file, it's better that remove the package-lock file and node_modules folder and then re-run the using npm install. then it might work for you

Actually, I had problems with the npm install. And that is why I had used the alternative method of downloading the nodes_modules folder from the given link and then directly running npm start. So now if I remove the node_modules folder, wouldn't that create the whole npm install issue again?

[Sonika2430]

This is what it looks like when I try to open the page. The same happens in google chrome too. I have made changes to the code in graph.tsk and app.tsk. Can that be an issue?

[marksainsbury]

#293 (comment) This works, its a huge file, there must be a better fix but Id rather get on with the task rather than sit and compare what its changed. you should be able to go straight to starting the client.

Thanks a lot for acknowledging and replying. I was on it actually and just started streaming data. Used this method only. Copied the node modules folder manually. Thanx a lot. Cheers!

I've done the same things by extracting the zip folder into the node_modules repo and replacing what's in there, but it's still showing the same error. Does anyone know why this isn't working?