Atmosphere loockup does not work if new package is referenced from package


#1

I am facing a weird problem with Atmosphere recently. If I try to reference a new package from package.js, like this:

  api.use('gadicc:blaze-react-component@1.4.0');

Meteor reports that the package is unknown.

However, ff I add it using

meteor add gadicc:blaze-react-component

the package can be downloaded and everything works just fine. I can now remove the package from package.json and reference it in the package instead. It will be found in this case. Anyone else facing this?


#2

I now had the same problem with a local package (inside /packages) not being found. What’s going on here?

Other packages worked just fine, but then I added a new one and Meteor didn’t find it. Adding it to packages.json worked, though.