What @sergiomeza88 mentioned is also good to cross match but here are some additional details which solved my problem and will help a lot to others as well.
Tip 1:
When you deploy the application on Firebase and try to access browser (especially React,Redux) application you may get an error saying :
can not find module "run" in bundle.js
So as mentioned in the answer it is must, and after this- you must execute the command:
npm start
This command will regenerate the
bundle.js and will not include/require the
"run" module which we were using while development. After this- you can deploy the latest bundle.js to the server.
Tip 2: In webpack.config inside output:{...}
section you should set path
and publicPath
to a new directory i.e. /public/. Otherwise on Firebase host when you mentioned 'public' directory as default directory to deploy - then it will create problem and application will not run on Firebase server.
Note: actually I am not sure and do not know how to tell firebase to use files on my root and not in my 'public' folder
But I think that outputting the webpack generated files and keeping other public files (css,html
) inside public folder is good as otherwise firebase deploy may upload other files sitting in root directory as well. (correct me if I'm wrong).
Ok so finally when you are updated the webpack.config output values as:
output: {
path: __dirname+ '/public',
publicPath: '/public/',
filename: 'bundle.js'
}
Then (finally making sure you are done with Tip.1 as well) and run the command to get latest bundle.js
npm start
. And finally you are good to go and deploy using:
firebase deploy
I believe you may have followed the initial steps of initiating
firebase login
and other init commands before running last deploy command.
Note: The "firebase serve"
command is also helpful to debug and test if application is running well on local machine then it will run well on live Firebase server as well.