You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Features; What is the motivation and/or use-case for the feature?
I try to migrate to this package from webpack-serve. We previously used process.env.WEBPACK_SERVE to see, if a project asks for a watch config or not. We'd like to keep a similar functionality without having every project to do add a process env on their own, before they call webpack-dev-serve. Maybe there could be a process.env.WEBPACK_DEV_SERVER flag.
FYI: This template says " Please note that we are NOT accepting FEATURE requests at this time." while in https://github.com/webpack-contrib/webpack-serve it's said "Please use webpack-dev-server (he is in support and update mode again). Feel free to create a issue if some features are not implemented in webpack-dev-server." ⚠
The text was updated successfully, but these errors were encountered:
Code
Old
WEBPACK_SERVE
usage in our config.For Features; What is the motivation and/or use-case for the feature?
I try to migrate to this package from
webpack-serve
. We previously usedprocess.env.WEBPACK_SERVE
to see, if a project asks for a watch config or not. We'd like to keep a similar functionality without having every project to do add a process env on their own, before they callwebpack-dev-serve
. Maybe there could be aprocess.env.WEBPACK_DEV_SERVER
flag.https://github.com/webpack-contrib/webpack-serve#setting-the-config-mode
FYI: This template says " Please note that we are NOT accepting FEATURE requests at this time." while in https://github.com/webpack-contrib/webpack-serve it's said "Please use webpack-dev-server (he is in support and update mode again). Feel free to create a issue if some features are not implemented in webpack-dev-server." ⚠
The text was updated successfully, but these errors were encountered: