Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couldn't install and run the server locally #12

Open
k-sai-kiranmayee opened this issue May 9, 2020 · 6 comments
Open

Couldn't install and run the server locally #12

k-sai-kiranmayee opened this issue May 9, 2020 · 6 comments

Comments

@k-sai-kiranmayee
Copy link

Hello! :)

What is done:

  1. Forked this repo
  2. Cloned it from there
  3. Now tried to install the dependencies

What is seen:

  • Seen while running the command npm install

image

  • To find what dependency was failing, installed one by one, and found that vue-fusioncharts was the one.

image

  • And this is what I get when trying to run the server

image

Versions/Machine configurations:

Node - 8.9.4
npm - 5.6.0
Windows - OS 10

Thank you!

@henryzt
Copy link
Owner

henryzt commented May 9, 2020

That's quite detailed! I'm not sure about the npm install error, could it be because of the version of node is outdated? @jieyouxu were you able to reproduce this?

For the error msg while running npm run serve, I think it might be because of the vue-cli-service is not installed or misconfigured on windows. You can try type vue -V in the command line to see if it is correctly installed.

If not, this and this might help!

@jieyouxu
Copy link
Collaborator

jieyouxu commented May 9, 2020

I don't think npm and node version is the problem here. I suspect it's related to vue cli only.

@jieyouxu
Copy link
Collaborator

jieyouxu commented May 9, 2020

After a closer look, I see that you have two problems:

  1. You can't seem to install vue-fusion-charts. This might be related to Windows? We'll have to diagnose this a bit more to tell.
  2. You can't run npm run serve. This is because you don't have vue-cli-serve installed.

To address (2), we shouldn't ask you to install @vue/cli globally. Instead @henryz00 can you add @vue/cli as a devDependency so developers don't have to install vue globally?

@henryzt
Copy link
Owner

henryzt commented May 9, 2020

To address (2), we shouldn't ask you to install @vue/cli globally. Instead @henryz00 can you add @vue/cli as a devDependency so developers don't have to install vue globally?

Makes perfect sense. Will do that tomorrow.

@k-sai-kiranmayee
Copy link
Author

Hey!! Thank you @henryz00 and @jieyouxu

Actually, for my work, I did install the Vue-CLI globally.

Removed all the node_modules and in the package.json, I removed the vue-fusioncharts and did npm i and viola! the dependencies are correctly installed and I could run the server 🥇 , however, still couldn't get the vue-fusioncharts installed.

  1. You can't seem to install vue-fusion-charts. This might be related to Windows? We'll have to diagnose this a bit more to tell.

Might be @jieyouxu.

And Vue version is 2.9.6

@jieyouxu
Copy link
Collaborator

jieyouxu commented Aug 22, 2020

I've tried to look for more info on this. This doesn't look like a vue-fusioncharts issue, but instead it looks like a npm bug. Specifically, the symptoms presented looks similar to those in https://npm.community/t/crash-npm-err-cb-never-called/858/96. Interestingly, the node and npm versions that you have seem to be the versions that people who use Linux/Unix revert to in order to workaround the "cb() never called" problems.

What's really happening here is that the npm 5.6.0 is swallowing the true cause of the Promise rejection. Possible causes:

  • Insufficient permissions.
  • Too many HANDLEs (a broader concept than file descriptors on Linux/Unix).
  • Your antimalware/antivirus software is blocking NPM from accessing these paths in the filesystem / reading/writing to memory.
  • Somehow a network request is failing due to proxies/firewalls.
  • ... the universe might well be collapsing because the true error cause is swallowed.

@k-sai-kiranmayee If you have the time, perhaps you could try to use a more recent Node version (i.e. latest LTS version) and more recent NPM version (the one that comes with the Node LTS version). I think they patched some error reporting in newer versions. That way, even if it does error out, at least we get to know why and how it failed and so we can try to help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants