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.markdown
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ var watchify = require('watchify');
90
90
91
91
## watchify(b, opts)
92
92
93
-
watchify is a browserify [plugin](https://github.com/substack/node-browserify#bpluginplugin-opts), so it can be applied like any other plugin.
93
+
watchify is a browserify [plugin](https://github.com/browserify/browserify#bpluginplugin-opts), so it can be applied like any other plugin.
94
94
However, when creating the browserify instance `b`, **you MUST set the `cache`
95
95
and `packageCache` properties**:
96
96
@@ -107,7 +107,7 @@ var b = browserify({
107
107
});
108
108
```
109
109
110
-
**By default, watchify doesn't display any output, see [events](https://github.com/substack/watchify#events) for more info.**
110
+
**By default, watchify doesn't display any output, see [events](https://github.com/browserify/watchify#events) for more info.**
111
111
112
112
`b` continues to behave like a browserify instance except that it caches file
113
113
contents and emits an `'update'` event when a file changes. You should call
@@ -240,7 +240,7 @@ to get just the library.
240
240
241
241
## rebuilds on OS X never trigger
242
242
243
-
It may be related to a bug in `fsevents` (see [#250](https://github.com/substack/watchify/issues/205#issuecomment-98672850)
243
+
It may be related to a bug in `fsevents` (see [#250](https://github.com/browserify/watchify/issues/205#issuecomment-98672850)
244
244
and [stackoverflow](http://stackoverflow.com/questions/26708205/webpack-watch-isnt-compiling-changed-files/28610124#28610124)).
245
245
Try the `--poll` flag
246
246
and/or renaming the project's directory - that might help.
0 commit comments