Meteor Windows Preview 0.2.0 with new installer

Hi Meteor forums!

As some of you may know, @slava, @avital, and I have been working hard on official Windows support for Meteor. We believe we are pretty close to completion of one of the most requested features in the history of Meteor.

Tonight, we are releasing a new preview version - WINDOWS-PREVIEW@0.2.0.

We unwittingly broke meteor update in the previous release, WINDOWS-PREVIEW@0.1.7, so use the new installer to update. Download it from the Windows preview Wiki page.

The biggest change in this release is the installer, which has been rebuilt completely using the popular WiX installer toolkit. If it doesn’t work for you, please report a bug on the Windows preview issue tracker.

Thanks so much to everyone who has been testing these releases so far - we wouldn’t have gotten this far without your continued feedback.


If we already have it installed would you prefer we use the installer to update?

Yes, it would be extra helpful to see how the installer works for that case! I’ll edit my original post to reflect that.

Installed fine. Though it sat at Installing Meteor... at about 20% for ~45 seconds or so and then made it to 100% in about 1 second. :smile:

After that I ran meteor --help and it downloaded meteor-tool@1.1.0-winr.8. First I saw a progress bar that took only about 10 seconds and then a spinner for about 60 seconds. Then I saw the expected output.

meteor update appears to have worked fine and I was prompted to create a Node.JS exception in the firewall.

Pretty normal stuff!

Did you run meteor --help from inside an app?

The first thanks, I try run meteor update but show:

C:\Users\Theara>meteor update

  if (p[0] === "\\" && (! partialPath)) {
TypeError: Cannot read property '0' of undefined
    at toPosixPath (C:\Users\Theara\AppData\Local\.meteor\packages\meteor-tool\1
    at Object.convertToStandardPath (C:\Users\Theara\AppData\Local\.meteor\packa
    at Object.files.getHomeDir (C:\Users\Theara\AppData\Local\.meteor\packages\m
    at defaultWarehouseDir (C:\Users\Theara\AppData\Local\.meteor\packages\meteo
    at Object.<anonymous> (C:\Users\Theara\AppData\Local\.meteor\packages\meteor
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)

This could be a bug in the tool that looks up the currently installed version by inspecting the meteor.bat script. What do you think, @sashko?

How does this get along with EACH-IN@0.0.3?
(sorry, I am still confused about Meteor installation/update process)

That seems possible - we changed the script at the last moment, but I didn’t think that would affect the script parsing because it was just changing the way the installation directory env var was set.

Here’s the commit:

Does it look like it would break the parsing?

Same error when I run meteor update

Got the same error over here (meteor update)

Updated using the installer. It’s such a shame that the Windows version is behind :frowning: I need to use Telescope but I can’t because it uses :frowning:

Seemed to install fine, but getting an error when I try to run any meteor whatever commands:

C:\Users\Kevin Guldenaar>meteor --help

C:\Users\Kevin Guldenaar\AppData\Local\.meteor\packages\meteor-tool\1.1.0-winr.11\mt\dev_bundle\lib\node_modules\fibers\future.js:245
TypeError: Cannot use 'in' operator to search for 'track' in null
    at C:\Users\Kevin Guldenaar\AppData\Local\.meteor\packages\meteor-tool\1.1.0-win
    at Array.forEach (native)
    at _.each._.forEach (C:\Users\Kevin Guldenaar\AppData\Local\.meteor\packages\met
    at Function._.pick (C:\Users\Kevin Guldenaar\AppData\Local\.meteor\packages\mete
    at [object Object]._.extend.getDefaultReleaseVersion (C:\Users\Kevin Guldenaar\A
    at Object.release.latestKnown (C:\Users\Kevin Guldenaar\AppData\Local\.meteor\pa
    at C:\Users\Kevin Guldenaar\AppData\Local\.meteor\packages\meteor-tool\1.1.0-win

Downloading meteor-tool@1.1.0-winr.12 -
Forever update on Windows 10 Technical Preview from version 1.0.7.

Downloaded and installed…

The Install progress bar completed to 100%* before anything happened, then meteor downloaded - ver steady 1% at a time increase.

After download it went ‘installing’ meteor but there was nothing to indicate activity because the progressbar was already at 100% but after a while, it changed to ‘publishing’ and then quickly to meteor installed.

*This could be a wix issue as I’m installing on win 2003 server - to give you an edge case :wink:

meteor update on a simple app with couple of packages
Dowloading meteor-tool@1etc outputs 1 line per every iteration of the progress bar (1000s of lines) then it hangs for a while…

Then I get same error as @theara

Yes, I did.

(Extra characters here for forum’s sake.)

Used the installer on top of the previous version.

The first time it gave me this error: (it might be a problem related to my firewall, it didn’t download anything), but ran it again and it installed successfully.

What are the Meteor versions packaged into these Windows releases?

I get the following error messing while doing a ‘meteor update’ on my windows machine:

if (p[0] === “\” && (! partialPath)) {
TypeError: Cannot read property ‘0’ of undefined
at toPosixPath (C:\Users\user1\AppData\Local.meteor\packages\meteor-tool
at Object.convertToStandardPath (C:\Users\user1\AppData\Local.meteor\pack
at Object.files.getHomeDir (C:\Users\user1\AppData\Local.meteor\packages
at defaultWarehouseDir (C:\Users\user1\AppData\Local.meteor\packages\mete
at Object. (C:\Users\user1\AppData\Local.meteor\packages\meteo
at Module._compile (module.js:456:26)
at Object.Module._extensions…js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)

These releases are coming straight off of devel, so they are actually the most up-to-date releases available.

Great news. Will try it tomorrow, hope that rebuilding the app is fixed by now.

1 Like