I am using Angular 7. Till last night it was working fine but since this morning whatever change I am making in the code is not showing in the browser. I have tried clearing browser history installing latest cli installing latest webpack but nothing is seems to work. I think I need to clear the node servers cache. Please help.
It was not a browser issue.
npm cache clear --force
did the magic for me
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.
Current Node Version: V15.3.0
Current Webdriver-manager Version: 7.0.15
I am at a loss. My end-to-end automated testing was running great, until the company I work for upgraded Google Chrome to 86.0.4240.111, previously we were using Chrome 83. So naturally with the update I ran the following command webdriver-manager update --versions.chrome=86.0.4240.111 however afterwards when I attempted to run my testing, I received the error stating that ChromeDriver only supports Chrome version 87. During this time I believe I had Node version V14.5.x or close to, Webdriver was version 6.14.x.
I talked with IT and we were unable to find an older version of Chrome from a trusted website to revert Google Chrome back, and so I upgraded Node and npm to the current versions stated above. Now after updating Webdriver-manager I get the error that ChromeDriver only supports Chrome version 87. I talked with IT and they will not upgrade to 87 even though it was released this past week.
My question is there any version which I can install Node and NPM in which I can use my testing with the current version of chrome which is 86.0.4240.111?
And what specific commands would I need to install the said version. Would it be npm install npm#[Enter Version Here]?
Thank you for taking the time to read and look at my question. If any more info is needed please let me know and I will gladly give you what I can!
Node version doesn't matter
npm version doesn't matter
You don't need to revert protractor
It's difficult to downgrade your browser, due to security concerns. You can only go up in version, but you can install any version of the chromedriver
what you actually need to do is to match a version of your local chrome to the version of chromedriver (the driver is the layer that controls your browser, so it's important to make them correspond to each other). So
First, find out what your version of chrome is. From your example I understand it is 86.0.4240.111
Then, find out what chromedriver version can be used. Take the major version of the browser (first 3 numbers, 86.0.4240 in your case) and find the corresponding version of the driver by going to this url https://chromedriver.storage.googleapis.com/LATEST_RELEASE_${CHROME_VERSION} (put the major browser version instead of ${CHROME_VERSION}). You'll see the chromedriver you're looking for is 86.0.4240.22
This is where the trickiest part begins. There are 2 installation of protractor usually:
local
global
I won't go over how to find which one you use, you can look it up. But when you find it, make sure you're updating the right one
When you know which protractor you're updating, go to it's folder and from that folder run npm i webdriver-manager#latest and then node ./bin/webdriver-manager update --gecko=false
when you updated the right webdriver, install the right chromedriver like so
node ./bin/webdriver-manager update --gecko=false --versions.chrome $VERSION
Make sure to put 86.0.4240.22 instead of $VERSION
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.
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.