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.
Related
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.
Coworker and I are trying to figure out why compilation times are different. We have the same exact Dell Laptop 7030 model, same SSD, same hard drive, same memory, specs. Our task manager process look similar.
Corporate orders the identical model computers.
We are downloading from Angular Git Repository, with config and package json, with same node size memory.
Question is, Initial build between our laptops is 2 min compared to 8 min.
When we edit a single word in same file, his only takes 5 seconds to recompile, my takes 20 seconds.
Only programs running on the identical computer is Angular command ng serve.
Does anyone have ideas to resolve this issue, and slow compile time?
Is there anything I can change in my work station to the compile speed similar?
Attemped the solutions for all coworkers, still slow
We have same Node.js versions
updated from Angular 8 to 10 in Company Project Git Repo
tried npm cache clear
attempted Uninstalling and Reinstalling Angular and Nodejs
ScanDisk from Windows does not show errors on SSD drive
compared package-lock.json with coworker, they are the exact same, compared in source control diff
turned on Windows Defender Exclusion on the Angular Git Folder
Resources:
Angular compilation slow
How to speed up the Angular build process
Update:
Just noticed my laptop really stalls on styles.scss file at 48%
As you described enough, All the things are the same, whether node or angular versions, Hardware models, software and configurations. You also ensured that build pipelines are the same.
The only thing which comes to mind is a few difference in dependencies, yes the version mismatch inside node_modules packages. Considering that when you dont specify exact versions like ^x.x.x (aka semantic versioning) includes everything greater than the particular version in the same major range for dependency to be installed by npm or yarn. There's a tool named npm semver to show this. In this way, You have to check the installed packages versions too, by opening each one and looking inside package.json file. Specially for those which you think affect the performance like sass loader. Performance for each release may be different.
If you are running exactly the same codebase.
I would with a high degree of confidence say that it is
node.js or different npm versions that is the problem
try running
node --version
npm --version
yarn --version
to see which versions of them you have installed.
for angular 9 I would suggest running node 12, which is the current LTS (Long Time Support) version.
until node 14 which is also out now, but it's LTS release is not until october 2020.
I find yarn to be magnitudes faster than npm, so if you want a speed boost try running that if you haven't tried it.
Also Try clearing the npm cache, as mentioned per comments.
npm cache clear
Has anyone got a clear simple path for installing node-gyp correctly.
I am moving away from C# etc to node development - and while I am a newbie with node.js - I am quite disappointed that the major issues I have had have been with a Microsoft related tool.
I need node-gyp ( I think ) to be able to use printers and connect to serial ports & barcode scanners - so I need to be able to get it going consistently or somehow avoid it all together.
I have successfully compiled on 2 different machines.. but it seems that anytime I have to do something on a new machine ( for something like electron or windows server ) - then I seem to spend hours trying to get it going.
The following line is supposed to work:
npm install --global --production windows-build-tools
And then when adding a package than needs node-gyp - I get the following error
The Windows SDK version 8.1 was not found.
That SDK is installed already ( and tried reinstaling ) . I can't believe how horrible this is to configure and I have read may posts online that don't help.
It seems utterly ridiculous to install packages and complete development environments that are many GBs to get this going.
help!
I think you have not installed Windows SDK 8.1 correctly. Here is the download link:
https://developer.microsoft.com/en-us/windows/downloads/sdk-archive
When the download has finish, restart your computer and adding package ;)
~XeCrafT
I am completely new to both Macs and Node.js, so sorry if this one is a bit basic.
I am running Mac OS X 10.5 (Leopard) and have just installed the last version of Node.js (released version, not built from source).
Whenever I attempt to run Node or do an NPM install, I get the following error message:
FATAL ERROR: CodeRange::GetNextAllocationBlock Allocation failed - process out of memory
Does anyone know what the problem is? If not, what would be the next steps to figure this out?
Edit: It turns out that if I run these commands a few times then they eventually work. So my work-around is to keep repeating the command until I get success. This is better than nothing but still not acceptable. Software like WebStorm, which needs to execute these tools, doesn't know about this workaround and fails all the time.
The issue seems to show up when running the distributed build of Node on anything pre OSX 10.6.
You can manually build the binary yourself if you don't have the option to upgrade your OS.
http://therobotsbrain.blogspot.com.au/2012/03/installing-nodejs-on-os-x-105.html
I'm running X.5.8, and node 0.10.13 was giving me this error message. I tried some earlier versions of node, and 0.10.3 works while 0.10.4 gets the error message. This is the x86 version, x64 seems to crash at .3 but works at .0. Oh wait, it's more complicated than that. Seems to make a difference when I make a symlink to the app in /usr/local/bin, it crashes. more often. Try a few different ones see which work for you.
I really need to get a new laptop.
download here: http://nodejs.org/dist/
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