Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set a process.env to see if webpack-dev-server was used #1532

Closed
1 of 2 tasks
donaldpipowitch opened this issue Oct 18, 2018 · 1 comment · Fixed by #1929
Closed
1 of 2 tasks

Set a process.env to see if webpack-dev-server was used #1532

donaldpipowitch opened this issue Oct 18, 2018 · 1 comment · Fixed by #1929

Comments

@donaldpipowitch
Copy link

  • Operating System: Mac OS
  • Node Version: 8 LTS
  • NPM Version: I use yarn
  • webpack Version: 4
  • webpack-dev-server Version: 3.1.9
  • This is a bug
  • This is a modification request

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 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.

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."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants