A Powerful and Highspeed Markdown Parser for Vue.
After installing via Yarn or NPM, use the following snippet in the script portion of the Vue component which you wish to render the Markdown.
After setting up the middleware in your vue component above, using the embedded markdown is as easy as writing it between the vue-markdown tags.
VueMarkdown has a default slot which is used to write the markdown source.
- TIP: The default slot only renders once at the beginning, and it will overwrite the prop of source!
- Copyright (c) 2016 miaolz123 by MIT.
- Permissions are not sufficient for npm to modify files.
I was having the same problem. I tried a
to turn off https. I also tried
to turn off the progress bar (it has been reported to slow down downloads).
The problem was with my network driver. I just needed to reboot and the lag went away.
You can try deleting
package-lock.json and running
npm install afterwards.This worked for me.
I had the same issue on macOS, after some time struggling and searching around, this answer actually solved the issue for me:
npm helped me on Mac OS. Use the command:
I am behind a corporate proxy, so I usually use an intermediate proxy to enable NTLM authentication.
I had hangs problem with npm install when using CNTLM proxy. With NTLM-APS (a similar proxy) the hangs were gone.
While your mileage may vary, running
npm cache verify fixed the issue for me.
When your ssh key is password protected run
ssh-add. npm probably hangs somewhere asking for your password.
It was strange but I guess I was just being impatient ran -> npm install --verbose and saw there was progress but it was just really slow!!! All I needed was patience :D
The registry(https://registry.npmjs.org/cordova) was blocked by our firewall. Unblocking it fixed the issue.
Incase its useful to others, the following is what worked for me:
On my machine, although npm proxy was set correctly,
npm install waits forever doing something like sill extract. Re-trying
npm install waits forever on the same package again and again.
After waiting for a long timeout,
npm install printed an error message implying that git was trying to fetch something.
The problem vanished after configuring git proxy using the below command:
https in the value of
http.proxy without which the configuration did not take effect. Proxy server settings (http / https / port) might vary for users; hence its worth spending a bit of time experimenting with npm and git proxy server settings.
With due respect to all the answers, I switched to a different network and it worked for me.
On MacOS, I was able to solve this by
After installing, you can revert to the original configuration with
Remove node_modules & package-lock.json from previous npm install and install again
If npm install loader is stuck and then pops up with..
npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! request to https://registry.npmjs.org/jest failed, reason: unable to get local issuer certificate"
Follow to uninstall Node.js and install properly
I personally had this issue and did all the steps I listed above. My issue was fixed with
npm config set strict-ssl false
This method is working for me when npm blocks in installation Package for IONIC installation and ReactNative and another package npm.
You can change temporary:
npm config set prefix C:\Users\[username]\AppData\Roaming\npm\node_modules2
Change the path in environment variables. Set:
Run the command to install your package.
Open file explorer, copy the link:
ok file yourpackage.CMD created another folder Created "node_modules2" in node_modules and contain your package folder.
Copy your package file CMD to parent folder "npm".
Copy your package folder to parent folder "node_modules".
npm config set prefix C:\Users\[username]\AppData\Roaming\npm
Change the path in environment variables. Set:
Now the package is working correctly with the command line.
I'm not sure if your problem is being caused by the same reason that mine was, but I too was experiencing a hanging "npm install" and was able to fix it.
In my case, I wanted to install typescript locally in the project:
For some reason this was conflicting with a global install of typescript that I had, and the shell was just hanging forever instead of finishing or erroring...
I fixing it by first removing the globally installed typescript with the -g global flag:
After doing this the first command worked! 👍
I had npm hanging on installation of electronjs on Windows 10. I reinstalled and still it was hanging. But I noticed it got installed on another desktop in the same network. So finally I found the culprit. The issue was caused by Bitdefender free edition. There was no warning by the antivirus but it was blocking it silently. Even the console was not closing once the installation starts as it kept hanging. Disable antivirus/firewall if its on Windows and make sure network is open as npm does not seem to have a proper way of communicating network blocks and will keep proceeding indefinitely.
For anyone on MacOS (I'm on Mojave 10.14), the following helped me out:https://github.com/reactioncommerce/reaction/issues/1938#issuecomment-284207213
You'd run these commands
npm install once more.
check your environment variables for http and https
The existing entries might be creating some issues. Try deleting those entries.
Run "npm install" again.
I just turn off my windows firewall and it worked for me.You can also try different versions of npm.
.npmrc file for a
registry entry (which identifies a server acting as a package cache.)
npm install would hang partway through, and it was because of a old / non-responsive server listed in my
.npmrc file. Remove the line or comment it out:
(And/or check with your IT / project lead as to why it's not working ;)
install nvm (Node Version Manager) and downgrade node version from 14 to 12 solved the issue in my case
Uninstalling and installing
npm worked for me. I'm using Ubuntu 20.04.1 LTS
In my case
npm install was hanging because it was waiting for me to input a password to my ssh key while cloning from git repository. There was no prompt and I realized this might be the case when I typed random character and nothing was echoed back. In my case I had to look at
package.json file and clone locally repositories listed there. Then I updated
package.json and changed paths of those git repositories to my local paths. After doing this everything else was installed without further errors.
On windows i suddenly had the same issue and tried all of the above, but the final solution for me was to switch off the ransomware protection which I had activated. It somehow doesn´t go well along with npm
I've hit this problem a couple times.
- When I was on VPN, I pressed Ctrl-C and disconnected from the VPN. Then
- When I wasn't on VPN, I pressed Ctrl-C and connected to the VPN. Then, again,
I was having this error because I was running npm in a (docker) container in WSL2, and docker in WSL2 was configuring the wrong nameservers in the containers, making the container unable to resolve hosts.
To see if your container (or even your host) can resolve hosts, you can try running:
curl https://github.com. In my case I received
curl: (6) Could not resolve host: github.com.
The error in the docker container doesn't happen if I don't use the default bridge, instead I used a custom bridge and defined the container with it, in which case the
resolv.conf file ends up with the correct nameserver:
127.0.0.11 corresponds to the docker DNS server, solving the problem in my case.
If you aren't running npm in a container, your issue may still be related to some misconfigured
resolv.conf file (if you are in a Linux machine, or in Windows with WSL/WSL2).
In case anyone else encounters this, I left the npm install to run for long enough, and then the Jest extension crashed (v4.2.1), at which point the npm install completed successfully.
The Jest configuration seems to show that a test auto-watch feature was enabled. I haven't changed any Jest settings as far as I'm aware, so this must be out-of-the-box functionality.
I had same issue when installing legacy version of vue tools (4.1.5).
node 10 worked for me.