rmariuzzo/config-webpack-plugin

💫 Merge one or more configuration files together with environment variables too.

Hi there 👋 – I'm Rubens!

On 2016, I was diagnosed with Hodgkin's Lymphoma a blood cancer, and I underwent chemotheraphy. On March 1st, the cancer returned, and I've started another chemotheraphy treatment on March 23rd, 2021. This can explain my slow response in some cases. If you would like more details, I have a blog for it. Happy coding!

• Currently working at X-Team as a full stack web developer helping leading companies to succeed.
• Owner of 75 open source projects that I try to maintain in my spare time.
• Recently, I have been working with React, TypeScript and Node. You can read more about my full experience here.
• I speak french, spanish, haitian creole and english. Right now, I'm learning italian.
• One of the admin of a Dominican developer user group with 6.6K members.
• Presented 3 tech talks in spanish.
• Attended a few conferences such as CodeCampSDQ, ReactEurope, GitHub Universe, Caribbean Developers Conference and NodeConf Colombia.

config-webpack-plugin's Issues

Add CI integration

Current situation

We don't have continuous integration...

Requirements

Configure the project to use Travis CI in different NodeJS env.

Details

• We should complete #4 to have some test in places.
• Configure a .travis.yml file.
• Add a gulp task for testing.

Create a landing page `config-webpack-plugin`

Current situation

We don't have any landing page to show off config-webpack-plugin. 😭

Requirements

While the README does a decent job, we would like to enhance the user experience providing a simple landing page which transmit in a clear way how config-webpack-plugin works.

Details

No details for the creative one. 😉

Add test cases

Current situation

We. Don't. Have. Tests. 😱 (I'm stupid brave enough to publish a plugin without any automated tests).

Requirements

We want to use a framework that can be plugged in our current build system.

Details

• Research for a suitable framework (maybe a framework that webpack use to test their official plugins).
• Test the merging of one file as is (with no changes).
• Test the merging of one file with changes due to one matching environment variable.
• Test the merging of multiple file with no matching environment variable.
• Test the merging of multiple file with one matching environment variable.

Support multiple configuration files

Current situation

The plugin can be configured with only one configuration file, which is fine to demonstrate that the plugin actually works.

webpack.config.js

const ConfigPlugin = require('config-webpack-plugin');
module.exports = {
    plugins: [ new ConfigPlugin('./config.js') ]
}

Requirements

We want to allow devs to specified more than one configuration file instead.

webpack.config.js

const ConfigPlugin = require('config-webpack-plugin');
module.exports = {
    plugins: [ new ConfigPlugin(['./config.default.js', './config.js']) ]
}

That way developers can merge configuration values from one or more files + environment variables.

Details

• The first parameter of config-webpack-plugin constructor should accept both a string and an Array.