Message "Failed to instantiate module growlNotifications..." appear on production env

George Jor

I am current using mean.io as development framework of my application and have been using growlNotifications plug-in for certain time and it works perfect on both server and client side.

while after some coding commit (does not affect the plug-in), the following error appear on the production server:

Uncaught Error: [$injector:modulerr] Failed to instantiate module acleague due to:
Error: [$injector:modulerr] Failed to instantiate module growlNotifications due to:
Error: [$injector:nomod] Module 'growlNotifications' is not available! You either...<omitted>...3) 

but it won't have any problem running on local. I ensure that the bower install work perfectly on production server and i did nth in the grunt file.

Could anyone help me or even give me some hints to solve this problem? Thanks a lot!

George Jor

As I was set the bower component as latest, the production server will run the bower update command to get the latest one while local does not.

So I upgraded the plugin and run it on both sides, it works now.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

From Dev

"message":"No living connections","node_env":"production"

From Dev

Configuring production env

From Dev

Javalite framwork in production env

From Dev

Mix.env/0 equivalent in production env?

From Dev

Alert message fails to appear

From Dev

Symfony 4, .env files and production

From Dev

React - Env variables in development AND production

From Dev

dotenv requires .env file on production

From Dev

react and redux error on production env

From Dev

Typescript transpile errors appear only on production server

From Dev

Making message appear in the middle of screen

From Dev

Why does this message appear in the inspect

From Dev

Browserify/Babelify React for production (NODE_ENV production)

From Dev

What is the difference between webpack --env.production and --mode="production"

From Dev

Precompiling assets with Rails_Env set as production

From Dev

Flask testing with pytest, ENV is set to production?

From Dev

Symfony .env secure passwords in production mode

From Dev

Heroku pipeline - staging env variable carried into production

From Dev

jquery doesn't execute in rails production env

From Javascript

React-native : detect dev or production env

From Dev

Leaflet Marker not found production env angular 7

From Dev

CKEditor doesn't work only in production env

From Dev

Using spawn function with NODE_ENV=production

From Dev

Phoenix equivalent of Rails.env.production?

From Dev

Log rails console always to file in production env

From Dev

Gatsbyjs .env.production variables not available in browser

From Dev

NODE_ENV after deployment becomes production?

From Dev

validation errors are added only in production env

From Dev

How to start foreman in production mode(ENV)

Related Related

HotTag

Archive