After upgrade to 1.3: Packages not available anymore about meteor-bower HOT 6 CLOSED

I think we'll be deprecating in favor of npm. If your package isn't
published there yet, you can copy or symlink the individual files you need
from .meteor/local/bower/* to eg vendor/*

On Tuesday, March 29, 2016, Marcos Cuevas [email protected] wrote:

Same here. After upgrading to Meteor 1.3 All the packages installed using
meteor-bower are not available. In my case most of them are modules for
angular and this is the message:

Error: [$injector:modulerr] Failed to instantiate module ngCordova due to:
Error: [$injector:nomod] Module 'ngCordova' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

If I remove the ngCordova injector from app.ng.js then the error message
is the following bower package

Error: [$injector:modulerr] Failed to instantiate module jett.ionic.filter.bar due to:
Error: [$injector:nomod] Module 'jett.ionic.filter.bar' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

Not sure if the problem is related to another bower issue that provokes
that "ignoredDependencies" does not work correctly and makes angular load
twice...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#113 (comment)

from meteor-bower.

Meteor 1.3 has a new build-in method to load JavaScript packages in your Meteor app, and it uses NPM. Because of that we have decided to deprecate this bower package. The build-in loader is way more robust (and officially supported by MDG) than this package.

Since the Meteor bundling system changed significantly I think we won’t work on a version of this package to support Meteor 1.3. That means that you will have to replace bower packages by NPM ones as part of the migration process from 1.2 to 1.3. If you don’t want to do that migration today, you could continue to use meteor-bower on Meteor 1.2 as of today.

from meteor-bower.

Same here. After upgrading to Meteor 1.3 All the packages installed using meteor-bower are not available. In my case most of them are modules for angular and this is the message:

Error: [$injector:modulerr] Failed to instantiate module ngCordova due to:
Error: [$injector:nomod] Module 'ngCordova' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

If I remove the ngCordova injector from app.ng.js then the error message is the following bower package

Error: [$injector:modulerr] Failed to instantiate module jett.ionic.filter.bar due to:
Error: [$injector:nomod] Module 'jett.ionic.filter.bar' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

Not sure if the problem is related to another bower issue that provokes that "ignoredDependencies" does not work correctly and makes angular load twice...

from meteor-bower.

Sorry @lorensr, I don't understand your answer and sorry again if I remake the question but I am using meteor-bower to install client side angular modules like ngCordova, angular-translate, etc.

After updating Meteor from 1.2.1 to 1.3 my app stopped working with the logs I CC.

My guess is that theres is something in the loading process in Meteor 1.3 update that prevents bower integrated libraries to load before the app.ng.js module does... but not sure.

from meteor-bower.

Ah okay, thank you for the information.

from meteor-bower.

Thank you @mquandalle and @lorensr. Now I understand!

from meteor-bower.