-
-
Notifications
You must be signed in to change notification settings - Fork 629
Incorrect warning about watch command #3778
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
Labels
Comments
|
But I see a problem |
@alexander-akait Looks like that fix worked, not getting the error in 5.1.1 any more. Thanks! |
silverwind
added a commit
to go-gitea/gitea
that referenced
this issue
May 12, 2023
- Update all JS dependencies - Tested citation and various vue components Also this includes the fix for webpack/webpack-cli#3778.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
After updating to 5.1.0, I'm getting the following warning when I run
npm run start
:However, this warning doesn't make sense – we're not using the
watch
command.The
start
command runs this command:webpack --watch --config webpack.development.js
It only uses
--watch
, notwatch
, and our webpack config doesn't include awatch
option. Switching--watch
towatch
makes the error go away.What is the current behavior?
The warning above is displayed even when it shouldn't be, based on the command used.
To Reproduce
Not sure – running the command above results in this error. This warning didn't show up in 5.0.1 (same configuration and command), so it has to have been introduced in 5.0.2 or 5.1.0.
Expected behavior
The warning above should only be output if the
watch
command is actually used.Additional context
The text was updated successfully, but these errors were encountered: