I’ve set-up a local folder where I store central packages I want to re-use across apps (using the PACKAGE_DIRS environment variable).
Two of my projects are still on Meteor 1.1, and I now wanted to create a new project from scratch using Meteor 1.2, to test out this new version.
However, I’ve run into a deadlock. One of my package.js files contains an asset, defined by the
isAsset: true option. AFAIR, this is the only way to define assets in Meteor 1.1, so I have to keep it this way until all apps are on 1.2.
However, this prevents my new Meteor 1.2 app to start. Although this app doesn’t even include the package, it crashes with this error:
While reading package from `/Users/waldgeist/Documents/Development/htdocs/packages/meteor/phantom`: package.js:52:7: The `isAsset` option to `addFiles` is deprecated. Use PackageAPI#addAssets instead.
It’s more than strange that a deprecated declaration prevents the whole startup. But what makes it even stranger is the fact that this package isn’t required by the app at all. Obviously, the fact that the package is located in the central package repository is enough to break everything. WTF?
Any ideas how to solve this? I cannot just use “addAssets”, since this would break the 1.1 apps that actually need the package. :-/