After installing node and Laravel in my new MacOs M1 Chip, when I run npm run watch
I get “terminal-notifier” cannot be opened because the developer cannot be verified on my Laravel project.
What I have done was to install npm i node-notifier and that didn't solve the problem.
I solved the problem by opening System Preferences then Security and Privacy
After App Store and identified developers on the Allow apps downloaded from:
There was an option to allow terminal notifier
N/B: Since I have already activated it, it's no longer on the image above
After activating that option, it solved the problem for me.
I hope this helps someone
Related
I know this is a noob question but I just start learning to code. I don't know why I cannot upgrade the current version of npm in my computer (5.5.1) to the newer one (8.1.2).
Can someone please help me with this?
There are couple of solutions I can think of:
Solution #1
Uninstall Node.js from your computer and install again. As the error message says, "use the version of npm that is bundled with Node.js". This is the preferred solution and very straightforward. Unless... you want to keep multiple versions of node in your computer, if that is the case, solution #2 will help.
Solution #2
Install a Node version manager (such as n). The package n allows you to download multiple versions of Node.js in your computer and switch between then when needed.
If the issue persists, you may have conflicting versions or directories in your computer. Please read this post about How to completely remove node.js from Windows. Then try re-installing from the website once you are done removing Node.
Good afternoon.
I've been fighting with Visual Studio Code for about a week now with an XMPie support rep and neither of us can figure out how to resolve this issue. My experience with React and Node.js is still beginner level as well, so if there is anything I'm obviously missing please let me know.
After launching a localhost for testing from VSC, when I attempt to work on a site skin in React, I get a "(node:77089) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated" everytime I save the change. As such, the localhost does not update in the browser.
The tech was able to finally replicate my issue by first installing node.js v14 and then downgrading to v12 which is the version that is approved.
I've done the following steps to try and fix the issue.
Uninstalled node and npm from the terminal
Verified/Deleted node related files/directories at:
/usr/local/lib/node_modules
/usr/local/lib/node_modules/npm/node_modules
/usr/local/include/node
/usr/local/lib/dtrace/node.d
/usr/local/lib/node_modules
/usr/local/share/doc/node
/usr/local/share/man/man1/node.1
/usr/local/systemtap/tapset/node.stp
Restarted, then reinstalled v12 of node.
However, the deprecated issue still remains and neither of us can figure out why that is. New user accounts exhibit this same behavior as well. Short of wiping and reinstalling the OS, I'm hoping to find out what we're missing to fix this issue. Thanks for your time and any assistance you can provide.
I installed node.js to work on a discord bot with VSCode but it didn't work.
I reinstalled it but ticked the 'install chocolatey' box this time, halfway through the installation I got 3 trojan alerts from my AV, and cancelled the installation.
Since then, I have been unable to uninstall, repair or reinstall Node.JS, through the Windows 10 uninstall function or from the Node.JS .msi file.
Each time I try, I get the same error message:
"The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed."
I've removed all instances of Node.JS from my program files and %appdata%, I've ensure the Installer Service is running, and yet the Node.JS application still shows in the Uninstall Tool and when I try to uninstall / modify / reinstall, it shows the same error, and seems to think it's still installed on my system! Not even Node.JS commands work in my CMD!
I've got no idea how to fix this, and I don't want to use glitch anymore to write my bot, so please help- or it seem's I'll have to factory reset my PC and hope that resolves the issue.
Thanks in advance, guys.
Godspeed.
EDIT: I tried installing a newer version hoping it would overwrite old Node.JS files. Didn't work. Issue still occurring.
Do these:
Open command prompt as Administrator and run /sfc scannow. It will scan and replace corrupted files.
Restart your PC when the scan is done.
System - Win 7 64 bit.
Nodejs - node-v6.9.4-x64.msi
Installation error - Another installation is in progress. You must complete that installation before continuing this one.
Solutions that did NOT work - Run as admin, Run via commandline as admin, log had same error i saw in installer, don't install online docs option,
Please help me to fix this. Thank you !
This will not be an issue with your NodeJs installation, it might be because of your previous installation (might be any other software) which might be still in progress or not exit properly.
To solve your issue, please try restarting your machine once and install. This will indirectly kill your previous unstable installation and allow you to install NodeJs
I had this issue with '2017-03-21, Version 6.10.1 'Boron' (LTS)'. Restarting my PC solved the issue.
P.S. However, this issue seems to be specific to the NodeJs installer. I tried installing other programs after the NodeJs installation threw up this error and they installed fine (even before the restart).
I'm in the process of developing an app for iPhone, using PhoneGap, and I'm using the PhoneGap developer tools provided for iPhone, that ports the built app to my local iPhone using a node server.
This was all work, and then without any apparent reason it suddenly stopped. Here's a screenshot.
It just hangs at this screen.
How many files in www folder have your project?
I had same problem when running phonegap serve.
I used bower to install my packages, and I noticed if I removed the folders of some of my project dependencies serve resumed to work again. One of my packages had more than 100 files (I needed only 2).
I made a cleanup and solved the problem.
I hope it helps.