AngularClass/NG6-starter

@syedz for what I know, there is no type of flag on the web app to distinguish between prod or staging, but you can create a script which is only added for production configuration with webpack and adds variables on the client that you need:
on webpack.config.js add app: [] as an entry:

module.exports = {
   devtool: 'source-map',
   entry: { app: [] },
   module: { /* ... */}
}

on gulpfile.bable.js replace:

gulp.task('webpack', ['clean'], (cb) => {
 const config = require('./webpack.dist.config');
 config.entry.app = paths.entry;

For:

gulp.task('webpack', ['clean'], (cb) => {
  const config = require('./webpack.dist.config');
  config.entry.app = paths.entry.concat(config.entry.app);

and Finally replace:

gulp.task('serve', () => {
  const config = require('./webpack.dev.config');
 config.entry.app = [
    'webpack-hot-middleware/client?reload=true',
  ].concat(paths.entry);

For:

gulp.task('browser-sync', () => {
  const config = require('./webpack.dev.config');
  config.entry.app = config.entry.app.concat([
      'webpack-hot-middleware/client?reload=true',
   ], paths.entry);

Now you can add the files on webpack.dist.config.js, overriding the entry.app to add this new file:

/* ... * / 
var config  = require('./webpack.config');
config.entry = {
  app: [
    path.join(__dirname, 'client/app/production.config.js')
  ]
};
config.output = {  /*... */ };