feat: add built in .env support
What kind of change does this PR introduce? Feature:
.envfile support following Vite's conventions- Only env variables prefixed with
WEBPACK_are exposed to Webpack-processed code - Env variables will also be available within
webpack.config.js
Did you add tests for your changes? Will add
If relevant, did you update the documentation? Will add
Summary Closes #3747
Does this PR introduce a breaking change? No
Other information This is my first PR, so there'll probably be a few mistakes / many questions
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: Sakib25800 / name: Sakibul Islam (98c9a1dc3cb121477397ac62c7191299dcb37476, dee25cee4d1c327f24ff96dfb6fc35e931f84e78, b94e50b1cadc0875d77cca1a34ac6937878dbc52)
@Sakib25800 could you see if you can resolve the merge conflicts again please? And maybe see if you change the branch to "ready for review" if it maybe gets reviewed a bit faster? It could be that the team is quite busy and they only look at the active pull requests. I am just guessing 😄
I completely forgot about this PR and didn't take it out of draft 😅.
Thanks @jpbnetley.