Drop browsersync completely in production build

Why in npm run build we still use browsersync? browsersync make sense for development. I deployed my app by running npm run build, expect everything to worked, but I saw movement on my app without me clicking anything, then I realised it was caused by browsersync.

What’s the purpose of browsersync in production and how to turn it off? just comment the config in tools/disServer.js ?

[coryhouse]

Slingshot generates static files to the dist folder. Browsersync is just set up so that you can run the production build on your local machine for review. For production, you should use a traditional web server to serve the static files written to /dist. So your deployment process really just needs to copy the files in /dist to your prod webserver.

[mikedevita]

unfortunately no I don’t. not even aware if there is an automated process for that part. typically we use http-proxy-middleware and reverse proxy to the sap back end during development. that way we only push to sap when were ready for a release and we know the UI is good to go.

I’m at SAP TechEd right now but shoot me an email [e-mail]:[e-mail] if you need further help since this is out of this kits scope and I’d hate to clutter the issue up with SAP stuff 😜.