This project uses Meteor 1.3-beta.10, which isn't available on Windows.
To work with this app on all supported platforms, use meteor
update --release METEOR@1.2.1 to pin this app to the newest Windows-compatible release.
Hehe…
I see… so it’s the same bug. Cheers!
I noticed a new beta come out but it doesn’t seem to be installable (the server does have internet access)?
me@dev:# meteor update --release 1.3-beta.11
Sorry, Meteor 1.3-beta.11 is not installed and could not be downloaded. Please check to make sure that you are online.
Looks like its not been pushed out yet. The version bump is little over an hour old so maybe give it another hour or two?
We’ll post here when beta.11 is ready. We’re merging a bunch of mobile and testing improvements into this release, so it’s a bit more complicated than the previous modules beta releases.
3 Likes
I’m having difficulty directly importing some of the npm packages that I’d previously been importing through @arunoda’s meteorhacks:npm package.
The issue seems to be that the __dirname object is not available within the imported package. Normally this and a few other objects are available to all nodejs modules. https://nodejs.org/docs/latest/api/globals.html#globals_dirname
I’m not sure how meteorhacks:npm handled this case but it seems like this should be something that meteor 1.3 should handle as well.
I can go back to the meteor hacks solution unless someone knows a workaround?
See https://github.com/meteor/meteor/issues/6055. Your issue should be fixed with the next beta (to be released shortly and announced here)
(BTW, which packages aren’t working?)
I’m still using beta 8. Is there any compelling reason to upgrade to beta 10, or should I stay put?
It’s a huge update, check out the number of commits.
1 Like
beta.8 was the last released version that is worth trying, and beta.11 will be the next, but beta.11 is not quite ready yet
2 Likes
I’m speaking more in terms of either tangible features or performance boosts, not necessarily the number of commits.
Cool, just the info I was looking for! Thanks, Ben.
Stoked for these testing changes!
What are they changing with testing? Did I miss something above? (hard to keep track, this thread is massive) 
Official testing by MDG! Finally!
3 Likes
5 Likes
I’ve upgraded to beta 11 and my project finally works again for the most part!
One of the remaining issues I’m having is that the Semantic UI fonts have stopped working:
OTS parsing error: invalid version tag
browse:1 Failed to decode downloaded font: http://localhost:3000/lib/semantic-ui/src/themes/default/assets/fonts/icons.woff
These worked before. Any ideas?