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.
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.
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
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!
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?
Hey @avital
So __dirname works now in beta-11! Thanks for that. But unfortunately busboy does not… it tries to read a file at that location but can’t find it:
fs.readdirSync(__dirname + ‘/types’)
Again, I’m not sure how @arunoda got this working with Meteorhacks:npm but its not working with the current beta-11 mechanism.
That’s because __dirname is not a full file system path, but simply the directory part of the absolute identifier of the current module. On the client, it doesn’t make sense to expose real file system paths, and it seemed risky to make the server and client behave differently. In an ideal world, the busboy package would just use require("./types/...") to load those types. What it’s doing now won’t work on Windows, anyway. There’s a chance we can make this work the way busboy expects, but I’m going to have to think about it some more. Thanks for the example!
Yeah I don’t disagree that there are better ways to do what they are doing. But it may be worth supporting on the server side as your likely to see more of it as people start sucking in npm packages.
Thanks for looking at it