refactor: use chained configs internally

This commit is contained in:
Igor Randjelovic
2020-11-14 15:23:44 +01:00
parent 9dd5471d6d
commit 2be179a8d0
10 changed files with 102 additions and 41 deletions

View File

@ -1,7 +1,25 @@
export { default as angularConfig } from './angular';
export { default as baseConfig } from './base';
export { default as javascriptConfig } from './javascript';
export { default as reactConfig } from './react';
export { default as svelteConfig } from './svelte';
export { default as typescriptConfig } from './typescript';
export { default as vueConfig } from './vue';
import base from './base';
import angular from './angular';
import javascript from './javascript';
import react from './react';
import svelte from './svelte';
import typescript from './typescript';
import vue from './vue';
// export final configs
// todo: perhaps we can export chain configs as well
export const baseConfig = (env) => base(env).toConfig();
export const angularConfig = (env) => angular(env).toConfig();
export const javascriptConfig = (env) => javascript(env).toConfig();
export const reactConfig = (env) => react(env).toConfig();
export const svelteConfig = (env) => svelte(env).toConfig();
export const typescriptConfig = (env) => typescript(env).toConfig();
export const vueConfig = (env) => vue(env).toConfig();
export interface IWebpackEnv {
hmr: boolean;
// todo: add others
}