Recently I did an update of my angular packages inside of a .net core application and after doing that I began running into 4 errors related to items inside the node_modules folder. I have read a couple of other similar issues on SO which did not help resolve this particular issue. It may worth noting that I can't seem to duplicate this on another laptop I have running the same code. I have attempted to revert back my angular version, deleted the node_modules folder and re-ran install of angular. To take a step further I've even completely uninstalled angular, updated node.js to the latest stable release and re-installed angular to no avail Any help resolving this would be much appreciated.
Related
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.
Starting from today, my builds started failing with errors related with node-sass.
After some research, I found the docker image was trying to find some binding.node that doesn't exist in the node-sass GitHub repository.
After a lot of failures, I realized the docker image I was using, was node:stretch and this image was updated 13 hours ago.
I tried to change to the previous version, node:11.14.0-stretch and the error is gone.
I know I fixed the problem for now, but was this the right procedure? Was there anything else I could do?
node-sass 4.12 has been released with support for Node 12. Because it is a binary module, it needs to recompile new bindings when new releases of Node are released. Pinning to "latest" or a non-specified version of the image can cause this to happen with a new Node release is made (which you figured out by re-pinning to a particular version).
I decided to upgrade my version of nodejs from 8.11.1 to 10.15.3. I am running on Windows 10 so I downloaded v10.15.3-x64.msi file. I created a brand new Angular application from "ng new" command and I got the "HTTP ERROR 400" page with no error in the console.
I have cleared the cache, reboot the system and nothing helps. When I will go back to node JS version 8.11.1 everything starts to work again. The newest version of nodejs v11.11.0-x86.msi also doesn't work for me.
How this can happen and how can I get any information what is going on?
EDIT: this is not a duplication of any existing topics about upgrading NodeJS, because the new version is seen by the system and all components - see the console result in the screenshot I provided. After upgrading the NodeJs all my solutions based on that technology stoped working showing HTTP Error 400 page. After degrading to v8 everything starts working again.
The problem came back when I had to install newer version of node (12.14.1), so this time it worked. Additionally I deleted folders that prompted from runnig where npm command after deleting an old version.
would anybody happen to know the latest versions that work together on Windows Vista? I've been back and forth trying to get the right combination together but ng new never works for some reason or another.
(this is the older post showing what I already tried)
I'm having a bit of a problem here. I attempted to update angular/cli and I got errors telling me I need to update my version of node. I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
I tried uninstalling angular and clearing the cache and installing angular-cli#1.0.0-beta.14 and it installs. I can create a new project with it though it takes a long time to create it, and it also throws an error with node-pre-gyp. I came across an article on Github that said it's meant to be installed locally in the project and not globally. So I tried uninstalling, clearing cache and installing without -g to make it local within my project folder and it still has errors installing and I still can't serve my project.
How can I clear this all up and just start back with a clean slate of Angular2? I've looked around and everything I find leads me to the docs which are now updated to something beyond what my computer can handle.
I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
Have you considered running Linux? There are many versions with a lightweight GUI that runs well on older hardware. Ubuntu Mate is an example. It's harder to run node on Windows because of symlinks.
My MonoTouch install is screwed somehow (MonoDevelop won't even open).
So yesterday I deleted /Developer/MonoTouch off my Mac because that was the only directions I could find for uninstalling it. Today I tried reinstalling both it and MonoDevelop. Both installers ran fine, but I still have the same issue so I went to "uninstall" it again...and that directory doesn't exist this time.
Then I went to install an older version (2.6.7) and that installer tells me that I have a newer version already installed.
So....what do I do?
I am in a very, very bad mood because of all this right now. A months worth of work is now pointless unless I can get this running again.
EDIT
I finally got an older version of MonoTouch to install. Version 2.6.7 that was downloaded off of their site. Now when I run MonoDevelop I get an error that says "MonoDevelop requires the Mono Framework version 2.6.7 or later" and gives me the option to "Cancel" or "Download".
This is the error that I got that started this whole thing. I installed 2.6.7 but it doesn't recognize, and if I install 2.8 it just won't launch (icon bounces 3 times then does nothing, no error, no app).
EDIT 2
The other thing of note is that no matter how many times I install/uninstall/reinstall any version of the Mono Framework, nothing at all shows up in /Developer/MonoTouch.
I don't know how important that is, but considering something used to be there until this problem started I thought it worth mentioning.
Also since this problem started, I can no longer open any .xib files inside of Interface Builder. Whether that means one created in XCode or opening Interface Builder then creating a new View. Interface Builder runs fine, but as soon as I try to open any .xib it crashes with this error report.
I notice it says something about libxml2 in there which WAS installed yesterday and is probably the root cause of this...but I have uninstalled and reinstalled that as well with no luck.
You need to install Mono 2.6.7 or later, please download and install:
http://ftp.novell.com/pub/mono/archive/2.8/macos-10-x86/10/MonoFramework-2.8_10.macos10.novell.x86.dmg