Creating a new folder under packages. packages/environment-variables-webpack-plugin. Does this name work?

Let's take dovenv-webpack-plugin

@alexander-akait if we do want to distribute it as a standalone plugin in the future, isnt it better to add it to the webpack codebase or put it under webpack-contrib org? creating it as a plugin here and then moving it to a different repo to distribute it additional unnecessary work
if we want this to be an inbuilt feature in webpack then lets add it to webpack repo or if its going to be an installable plugin then lets create a new repo under the contrib org?

@burhanuday That's right, we can do it this way, but I'd rather keep it here for better integration with CLI (i.e. allows to have special flags for this) and fast fixes and fast releases, not sure it really make sense to use it as standalone plugin (except complex cases)

Okay. Creating new package here then

The main goal is a seamless integraiton, moving it and rename is not long task, implementation is the most long task

Codecov Report

Attention: Patch coverage is 99.04762% with 1 line in your changes missing coverage. Please review.

Project coverage is 91.77%. Comparing base (78f57d1) to head (ccf341e).
Report is 353 commits behind head on master.

@@            Coverage Diff             @@
##           master    #3759      +/-   ##
==========================================
+ Coverage   91.64%   91.77%   +0.13%     
==========================================
  Files          22       23       +1     
  Lines        1628     1776     +148     
  Branches      466      505      +39     
==========================================
+ Hits         1492     1630     +138     
- Misses        136      146      +10     

since env param in the cli is already taken, what should we use for passing array of env file names in the cli?
does env-file work?

• let's add test case for const { DB_HOST, DB_PASS } = process.env; (we supports it in webpack, just to check it), same for import.meta

@alexander-akait

In this plugin we are defining the variables using string like "process.env.varname":"value" and not the object syntax. Object syntax would be required for the above test case to pass.

While figuring this out, i was reading the webpack docs for define plugin and saw that this is recommended against doing in a note on this link - https://webpack.js.org/plugins/define-plugin/#usage

Other than that, i have implemented allowEmptyValues and set default value to false. also added tests for it as well as docs

@alexander-akait friendly ping

@burhanuday yeah, sorry for delay, on my TODOs list on the top after #3739,

web-infra-dev/rspack#2208 this is also the requested features from rspack users, glad to see webpack-cli is willing to support it

@hardfist Yeah, it will be an official part of webpack ecosystem, I want to be align with next.js logic, it is flexible and solves almost all requests, hope we will finish it soon (this week)

@burhanuday I think also we need to check how the new node --env-file option could be used alongside this. Wil review your PR soon! :)

@ Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@snitin315 Please review the new changes.