Everything happens with Meteor 1.1.0.2
I've been developing a meteor app for quite some time now and with the 1.1 release of meteor I switched my dev environment from linux VM to Windows 8.1 (my everyday working machine). Everything has been working great so far, no issues being present at all, until today.
After deploying my app today, everything seems to work fine for 10-15 seconds and then the app crashes and console starts to throw the following error, which is thrown continuously, every second:
W20150504-14:21:21.355(2)? (STDERR) wmic spawn error: Error: spawn ENOENT
What's important to note is that I did not touch any core files prior to this thing happening and that the problem occurs only on my machine (my co-worker uses Windows 7 and everything works fine) and it is bound only to this particular project.
Here is a list of packages I use, maybe it will give you a hint as to what it might be:
meteor-platform
iron:router
ddp
accounts-password
jquery
meteorhacks:fast-render
meteorhacks:subs-manager
meteorhacks:npm
accounts-ui-bootstrap-3
twbs:bootstrap
upload-jquery
reactive-var
fortawesome:fontawesome
mizzao:jquery-ui
edgee:slingshot
check
tracker
fourseven:scss
npm-container
sacha:spin
meteorhacks:cluster
aldeed:autoform
ovcharik:alertify
mjn:famous
gadicohen:famous-views
meteorhacks:kadira
I've managed to resolve this issue by removing Kadira from my project. I still have no idea why did it make my Windows 8.1 throw ENOENTs so if anyone knows, I would really appreciate your input.
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.
So, I've been trying to build a MEAN (MongoDB Express Angular NodeJS) stack server to use for academic teaching purposes, as a student sandbox/training environment. I can install all packages fine, the problems appear when trying to generate a new project inside my Linux box. It always halts towards the end, with an error about "Busy File" or something along those lines, and thus the project is missing crucial files to run with the command 'ng serve'.
Another problem is the sync between host and guest, I am running Windows 10 as host, and using Debian 9 as the guest, and when editing and saving files on the host, NodeJS compiler is not triggering nor synchronizing my changes to the server.
I've tried some Vagrant plugins, such as FS-Notify and WinNFSD, but to no luck. I remember reading something about Nodewatch being the culprit, but I am not sure and I don't have much experience around Angular, Node and Vagrant together.
I've browsed the Github repository Vagrant Plugins, https://github.com/hashicorp/vagrant/wiki/Available-Vagrant-Plugins, but can't seem to find an appropriate solution to run an isolated MEAN stack Debian with only Vagrant and VirtualBox on a Windows host.
I am using Windows 10 as host, Debian 9 as the guest. Windows host is using Vagrant 2.1.4, and VirtualBox version 5.2.18. (I've tried using Docker, but it requires and consumes too many resources, unfortunately.)
I've noticed that there seem to be quite a few people with similar issues.
I would greatly appreciate any help or input on what to do. Thank you in advance.
https://blog.entrostat.com/vagrant-ubuntu-docker-windows/
Following this article worked just fine for me.
Don’t forget to start a second PowerShell and run
vagrant fsnotify
The only issue I’m currently trying to resolve is tslint going crazy in VS. Code and WebStorm due to the host system not containing node_modules.
I’ll get back here when I find a solution.
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.
I'm running node.js on FreeBSD box, in a jail. I made an upgrade of Node.js from 0.12.7 to 4.1.1 and my configuration for daemontools stopped working - I get EPIPE errors and it keeps restarting and overwhelms the machine.
If I execute the same script in an terminal it runs fine.
Can somebody please help me with this
Thanks in advance
To make it work I switched from daemontools to runit - now it works like a charm
Try re installing it. I faced same problem, and I fixed it by reinstalling it.
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/