adding support to pass Env param to webpack

This commit is contained in:
Jordan McDonald
2017-10-06 15:41:05 -05:00
committed by Steve Sanderson
parent e7ffb8bb71
commit 7c07beb494
2 changed files with 7 additions and 1 deletions

View File

@@ -50,5 +50,10 @@ namespace Microsoft.AspNetCore.SpaServices.Webpack
/// the webpack compiler.
/// </summary>
public IDictionary<string, string> EnvironmentVariables { get; set; }
/// <summary>
/// Pass in the env parameter to webpack.
/// </summary>
public object EnvParam { get; set; }
}
}

View File

@@ -32,6 +32,7 @@ interface DevServerOptions {
HotModuleReplacementServerPort: number;
HotModuleReplacementClientOptions: StringMap<string>;
ReactHotModuleReplacement: boolean;
EnvParam: any;
}
// We support these three kinds of webpack.config.js export. We don't currently support exported promises
@@ -248,7 +249,7 @@ export function createWebpackDevServer(callback: CreateDevServerCallback, option
// In the future, we could add support for configuring the 'env' param in Startup.cs. But right
// now, it's not clear that people will want to do that (and they can always make up their own
// default env values in their webpack.config.js).
webpackConfigExport = webpackConfigExport();
webpackConfigExport = webpackConfigExport(options.suppliedOptions.EnvParam);
}
const webpackConfigArray = webpackConfigExport instanceof Array ? webpackConfigExport : [webpackConfigExport];