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
Copy file name to clipboardExpand all lines: README.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -210,7 +210,7 @@ please see the [webpack documentation](https://webpack.js.org/configuration/watc
210
210
Type: `Boolean|Function`
211
211
Default: `false`
212
212
213
-
If true, the option will instruct the module to write files to the configured
213
+
If `true`, the option will instruct the module to write files to the configured
214
214
location on disk as specified in your `webpack` config file. _Setting
215
215
`writeToDisk: true` won't change the behavior of the `webpack-dev-middleware`,
216
216
and bundle files accessed through the browser will still be served from memory._
@@ -231,6 +231,17 @@ of `true` _will_ write the file to disk. eg.
231
231
}
232
232
```
233
233
234
+
### fs
235
+
Type: `Object`
236
+
Default: `MemoryFileSystem`
237
+
238
+
Set the default file system which will be used by webpack as primary destination of generated files. Default is set to webpack's default file system: [memory-fs](https://github.com/webpack/memory-fs). This option isn't affected by the [writeToDisk](#writeToDisk) option.
239
+
240
+
**Note:** As of 3.5.x version of the middleware you have to provide `.join()` method to the `fs` instance manually. This can be done simply by using `path.join`:
241
+
```js
242
+
fs.join=path.join// no need to bind
243
+
```
244
+
234
245
## API
235
246
236
247
`webpack-dev-middleware` also provides convenience methods that can be use to
0 commit comments