I’m not sure what the minimum version of Meteor needed for this is, but if you symlink that package in to your project hierarchy (like under /imports somewhere) then the meteor build system will recompile that package. In Meteor 1.8.2+ you can just set a recompile flag for that specific npm package.
I’ve had issues like that on occasion. I think it happens when the version of Mongo changes between versions of Meteor. You can either manually migrate your data, or you can meteor reset your local project and start fresh.
Oh! For atmosphere packages, you’ll need to get the package author to update it with the ecmascript package and republish, or you can grab a copy from source, and put it in your local /packages folder, and then adjust it as needed (add the ecmascript package to the package’s package.js file).
Update: Actually, it looks like the package is configured correctly - does it just need to be republished? Or maybe it just doesn’t support Meteor 1.6 any more? I’d probably file an issue in Meteor.