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 the sake of test, I've deleted my previously generated bundle.js and run webpack-dev-server. Output:
C:\sites\YDR\branches\refactoring\development>webpack-dev-server
[11:27:38] [write-file-webpack-plugin] options { exitOnErrors: true,
force: true,
log: true,
test: null,
useHashIndex: true }
http://localhost:8080/
webpack result is served from /
content is served from ./
(... typical dev-server output ...)
But no bundle.js is created anywhere.
The text was updated successfully, but these errors were encountered:
I suspect it's an issue with resolving path. You bundle may have been created elsewhere. Check every directory up the chain from the path specified including the root of C: drive.
I'm having the same issue... My issue is specific in that if I undo a change and save (so I already saved once in that state and undo to return to that state after saving in a different state) webpack is trying to refer me to the previous version that I just removed(because i'm deleting before rewriting). It's crazy... webpack remembers that it just wrote that same file and instead of rewriting just changes itself to refer back to the previous version.
I just question what force is supposed to do? It's defiantly not forcing a new write in that situation.
I don't get it how it's supposed to work.
I'v added write-file-webpack-plugin to my
webpack.config.js
:var WriteFilePlugin = require('write-file-webpack-plugin');
and included it in plugins:
Also, I've set devServer's outputPath to be the same as output.path as you recommended:
For the sake of test, I've deleted my previously generated bundle.js and run webpack-dev-server. Output:
But no bundle.js is created anywhere.
The text was updated successfully, but these errors were encountered: