So, I did the following as mentioned in the starting steps here :
And tried to run localhost on my browser but got the message that the site can’t be reached. I am little bit confused about the instructions, I did meteor npm install. I don’t understand what does another meteor command means as I highlighted in the image above. Just wondering if I need to perform additional steps to make it work? Thanks
Did you browse to localhost:3000 or just localhost (needs to be the former).
Also, you will need to wait while Meteor builds the application. You can browse anytime after it reports the proxy has started, but the app won’t actually be available until it reports the application as being ready (may take several minutes on the first run as assets are downloaded and built).
Yes, I did use localhost:3000. I tried checking just now and it’s still the same message. Is there any particular time period I should consider waiting before checking again?
Your console window should be reporting progress as it builds the app. You may get several messages as it checks/downloads and builds, but the key stages are:
=> Started proxy. <-- You can browse to localhost:3000
=> Started MongoDB.
=> Started your app. <-- Your app will now be available
=> App running at: http://localhost:3000/
How long it takes is hard to say, except it does take a lot longer on Windows than on Linux. I develop Meteor on both, but Linux is the better experience (I use a Virtualbox VM under Windows).
Here is what I see after executing the commands for installation. I don’t see “Started” messages on my side. Please find my messages below:
d:\Users\myname>cd simple-todos
d:\Users\myname\simple-todos>meteor npm instal
imple-todos@ d:\Users\myname\simple-todos
-- meteor-node-stubs@0.2.3
+-- assert@1.3.0
+-- browserify-zlib@0.1.4
| `-- pako@0.2.8
+-- buffer@4.5.1
| +-- base64-js@1.1.2
| +-- ieee754@1.1.6
| `-- isarray@1.0.0
+-- console-browserify@1.1.0
| `-- date-now@0.1.4
+-- constants-browserify@1.0.0
+-- crypto-browserify@3.11.0
| +-- browserify-cipher@1.0.0
| | +-- browserify-aes@1.0.6
| | | +-- buffer-xor@1.0.3
| | | `-- cipher-base@1.0.2
| | +-- browserify-des@1.0.0
| | | +-- cipher-base@1.0.2
| | | `-- des.js@1.0.0
| | | `-- minimalistic-assert@1.0.0
| | `-- evp_bytestokey@1.0.0
| +-- browserify-sign@4.0.0
| | +-- bn.js@4.11.1
| | +-- browserify-rsa@4.0.1
| | +-- elliptic@6.2.3
| | | +-- brorand@1.0.5
| | | `-- hash.js@1.0.3
| | `-- parse-asn1@5.0.0
| | +-- asn1.js@4.5.2
| | | `-- minimalistic-assert@1.0.0
| | +-- browserify-aes@1.0.6
| | | +-- buffer-xor@1.0.3
| | | `-- cipher-base@1.0.2
| | `-- evp_bytestokey@1.0.0
| +-- create-ecdh@4.0.0
| | +-- bn.js@4.11.1
| | `-- elliptic@6.2.3
| | +-- brorand@1.0.5
| | `-- hash.js@1.0.3
| +-- create-hash@1.1.2
| | +-- cipher-base@1.0.2
| | +-- ripemd160@1.0.1
| | `-- sha.js@2.4.5
| +-- create-hmac@1.1.4
| +-- diffie-hellman@5.0.2
| | +-- bn.js@4.11.1
| | `-- miller-rabin@4.0.0
| | `-- brorand@1.0.5
| +-- inherits@2.0.1
| +-- pbkdf2@3.0.4
| +-- public-encrypt@4.0.0
| | +-- bn.js@4.11.1
| | +-- browserify-rsa@4.0.1
| | `-- parse-asn1@5.0.0
| | +-- asn1.js@4.5.2
| | | `-- minimalistic-assert@1.0.0
| | +-- browserify-aes@1.0.6
| | | +-- buffer-xor@1.0.3
| | | `-- cipher-base@1.0.2
| | `-- evp_bytestokey@1.0.0
| `-- randombytes@2.0.3
+-- domain-browser@1.1.7
+-- events@1.1.0
+-- http-browserify@1.7.0
| +-- Base64@0.2.1
| `-- inherits@2.0.1
+-- https-browserify@0.0.1
+-- os-browserify@0.2.1
+-- path-browserify@0.0.0
+-- process@0.11.2
+-- punycode@1.4.1
+-- querystring-es3@0.2.1
+-- readable-stream@2.0.6
| +-- core-util-is@1.0.2
| +-- inherits@2.0.1
| +-- isarray@1.0.0
| +-- process-nextick-args@1.0.6
| `-- util-deprecate@1.0.2
+-- stream-browserify@2.0.1
| `-- inherits@2.0.1
+-- string_decoder@0.10.31
+-- timers-browserify@1.4.2
+-- tty-browserify@0.0.0
+-- url@0.11.0
| +-- punycode@1.3.2
| `-- querystring@0.2.0
+-- util@0.10.3
| `-- inherits@2.0.1
`-- vm-browserify@0.0.4
`-- indexof@0.0.1
d:\Users\myname\simple-todos>
So where’s the meteor command you used in the OP? You need to do that before you get any of the messages I’ve shown.
meteor is equivalent to meteor run - it builds and runs the application in dev.
Okay, Thanks. I didn’t do that. It was slightly confusing for me as I mentioned in the screenshot. It’s showing the start messages now after running meteor command.
Cool. Glad you got it working. 