I’ve only heard about Windows 10’s bash today. Installed the bash application, installed meteor, installed node, installed npm. Only minor errors during the the process. Now running meteor on windows with all the code refresh speed of linux.
Unfortunately, only a tiny fraction of our users are on Windows 10. Perhaps this could encourage people to upgrade, but I don’t know if it’s a viable strategy for most people? Maybe we can add something to the website so that people can make the choice themselves.
It’s odd that you needed to install npm and node separately… we should see why that is, since Meteor includes those things.
Hi Sashko, I understand that Windows isn’t as high priority as other platforms. I usually lean towards Linux myself, but I’ve been quite happy with Windows 10 on this laptop, especially if I can run native bash.
No ideia why node/npm have to be installed separately. I was also under the impression meteor included them.
Another curious error is when I run meteor through bash, even though it runs fine, I receive a warning before MongoDB starts message saying: Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/
This message does not show up when I run meteor through Windows. If I perform a meteor reset through bash, it seems the database engine is upgraded, since the warning does not show up anymore, but MongoDB becomes unable to start (both in bash and windows). While starting meteor project, during MongoDB start I receive an “unexpected mongo exit” error.
If I perform another meteor reset, this time on windows, the engine seems to be reverted (I start receiving the engine related warning messages on bash) but everything else works properly.
When using powershell to run meteor the cmd line interface gets distorted but the meteor app runs. Hope it is fixed. So now I went back to the basic command line (cmd) and it works. Perhaps I will install bash