I am trying to teach myself how to use the MEAN stack and I am working through the docs from the MEAN.io site. I am at the point where I run the following commands:
$ npm install -g mean-cli
$ mean init <myApp>
$ cd <myApp> && npm install
and these run just fine. But when I get to the next step which is to either just run
gulp
or
node server
and nothing happens. If I run gulp then after it gets to the part where it says
Finished 'development' after 6.15 μs
in the logs it just hangs there. If I run node server it just hangs and nothing else happens. In either case I see nothing at
http://localhost:3000/
Is this a common sticking point for people?
Related
When creating a react app, I run these commands in my terminal:
npx create-react-app app-name
npm install
npm start
npm start allows me to view my project locally, but I accidently closed my terminal before running ctrl + c to end it. The browswer tab containing localhost 3000 (the npm start default host) has been closed for a while now, but my project can still be viewed there everytime I follow that link. Now everytime I run npm start it tells me that localhost 3000 is taken and I have to input another command and run it on localhost 3001. I've made this mistake a few times. I don't mind doing this, but it got me wondering if there is a global version of ctrl + c that will close all of these at once.
Firstly, I think you've had a misconceptions here: closing the browser tab will never end the server that you've started (i.e. the server npm start created).
For your question I think you can use the approach of killing a process based on the port they're occupying in this question:
Find (and kill) process locking port 3000 on Mac
I'm having this problem "error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening starter.xcodeproj. Run CLI with --verbose flag for more details." since I pulled the latest update from the other colleague, I can't run the project in my simulator, but my colleagues side works fine.
I've tried to change the build system to legacy build system.
Clone the project again.
remove the build folder under iOS folder, and run again.
remove the node module folder and run again.
I have tested in different device is not working too.
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening starter.xcodeproj. Run CLI with --verbose flag for more details.
User defaults from command line:
IDEDerivedDataPathOverride = /Users/nexplatform/Desktop/padini scm mobile/SCM/ios/build/starter
brew install cocoapods
cd projectfolder/ios
pod install
and
cd..
react-native run-ios
DroidEdit allows you to run commands if you have sl4a installed and the am command works wonderfully... I was wondering if there is a way to use am to launch an app with params .. specifically I want a command that will tell termux to run a command on a file that I specificy ... so far I found this snippet that launches the termux app .. now how do I get it to run node or webpack from npm as well?
am start --user 0 -n com.termux/com.termux.app.TermuxActivity
I am following a tutorial, and I am supposed to have a gulpfile.js running, but I'm encountering a strange situation. Gulp works in one location and does not work in the other.
I have a dual boot for Ubuntu and Windows 8.1. In the Ubuntu OS Documents directory the gulp command does not work, but returns an error saying "'gulp-plumber' not found". I don't understand why since the folder structure is exactly the same. If I change directory to the windows volume and access the main project folder, when I type "gulp" everything works fine.
Additionally, if I CTRL-C in the command line, the gulp command stops working and returns an error saying:
events.js:163
throw er; // Unhandled 'error' event
Error: write EPIPE
So how can I run the gulp command again? Is it through ps aux, check something running and then kill it?
github.com/DannyS95/Project
This issue has been fixed, i had to install gulp plumber, because i did not have that package in the package.json file.
Then a quick npm install, and since i have gulp globally i can just run gulp and voila, it works.
I'm having trouble running Docco on Windows 7. I did the following:
downloaded and installed python and perl
installed node js
Run npm install -g coffee-script
Run easy_install pygments
Run npm install -g pygments
Run npm install -g docco
I navigated to the directory with javascript source:
C:\javascript>docco animation.js
docco: animation.js -> docs\animation.html
fs.js:427
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT, no such file or directory 'C:\javascript\docs\animation.html'
at Object.fs.openSync (fs.js:427:18)
at Object.fs.writeFileSync (fs.js:966:15)
at write (C:\Users\myaccount\AppData\Roaming\npm\node_modules\docco\docco.js:111:15)
at C:\Users\myaccount\AppData\Roaming\npm\node_modules\docco\docco.js:29:11
at fs.js:266:14
at Object.oncomplete (fs.js:107:15)
Any idea what the problem is?
Looking at the Docco sources, this is the problem:
ensureDirectory = function(dir, callback) {
return exec("mkdir -p " + dir, function() {
return callback();
});
};
In other words: it assumes that an executable called mkdir exists, and uses it to creates the necessary directories (including the output directory). But mkdir is a Unix-ism, and (usually) not available on Windows. So it fails (and since Docco isn't checking for any errors, it happily continues as if nothing happened...).
EDIT: seems these issues were fixed recently, so if you use the Github-hosted version of Docco you might get it to work.