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
Consider the following JS file index.js (the only file in a folder):
var k = 0;
I'm trying to start webpack in watch mode:
webpack index.js bundle.js --watch
When my work folder is c:\dev\, everything works as expected. But if I work in folder c:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\, webpack doesn't rebuild project after I change index.js file.
Expected/desired behavior:
Watch mode should work in any folder.
Notes
I tried to understand the source of the problem. Looks like npm module is-glob (dependency list: webpack->watchpack->chokidar->is-glob) thinks that c:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\ is a glob and watchpack tries to listen changes in wrong not existing directory (c:\Program Files x86\Apache Software Foundation\Apache2.2\htdocs\?).
I'm submitting a bug report
Webpack version:
1.13.2
Please tell us about your environment:
Windows 7
Current behavior:
Minimal test case.
Consider the following JS file
index.js
(the only file in a folder):I'm trying to start webpack in watch mode:
When my work folder is
c:\dev\
, everything works as expected. But if I work in folderc:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\
, webpack doesn't rebuild project after I changeindex.js
file.Expected/desired behavior:
Watch mode should work in any folder.
Notes
I tried to understand the source of the problem. Looks like npm module
is-glob
(dependency list:webpack
->watchpack
->chokidar
->is-glob
) thinks thatc:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\
is a glob andwatchpack
tries to listen changes in wrong not existing directory (c:\Program Files x86\Apache Software Foundation\Apache2.2\htdocs\
?).Maybe, it will help you to fix this bug!
Moved from webpack/webpack#2994
The text was updated successfully, but these errors were encountered: