Rebuild does not happen ever

[franleplant]

Hi!
I've used watchify several times without problems, but right now it's not working for me.
This is the command I'm running:

watchify -v -t babelify js/index.js -o js/bundle.js

This are my specs:

• OS X Yosemite 64 bit
• Zsh
• Watchify 3.1.0

Any ideas how to solve this?

Thanks!
Fran

[mattdesl]

Working for me. My specs:

• OSX yosemite (10.10.1) with regular terminal
• watchify 3.1.1
• babelify 6.0.2
• npm 2.8.2
• node 0.10.32

It could be you are running an old version of watchify (e.g. global install), or maybe something to do with the babel transform.

I would do this:

npm install watchify babelify --save-dev

And add a scripts to your package.json; this will run the local version:

"scripts": {
    "watch": "watchify -v -t babelify js/index.js -o js/bundle.js"
}

Now npm run watch and see what happens. This will help rule out a few things. 😄

[franleplant]

@mattdesl your suggestion did not work. I was already working with and without npm.
I've done some additional steps nevertheless.

• Update npm, now my version is 2.7.2
• Checked my node version: 0.12.2
• Babelify version 6.0.2

Another clue is that Im using Vim to edit files, I suppose that is not relevant at all but I state it nevertheless.

Perhaps the problem is fsevents.
Also, I might need to restart my computer, but it's impossible right now 😄

Thanks a lot for your help.

Fran

[franleplant]

Just for the sake of removing obvious things I've tried:

• Running the npm task as sudo
• Changing the source files permissions: sudo chmod -R 777 .

I didnt work

[rashkov]

I am having issues with Vim as well. It actually does run the first few times that I save, and then it stops watching whatever file I'm working with. I think this has to do with how Vim saves. I think it does a "safe write" which fully replaces the file at once.

[zertosh]

@rashkov I saw your vim issue, I'll look into it. @franleplant Are you also using vim? If not, what editor?

[franleplant]

Im also using vim!
I tried with Sublime Text 3 with no differences.

[rashkov]

Sublime text doesn't have this problem for me, and emacs either. Only Vim gives me trouble. So we are probably looking at two different issues.

[franleplant]

@rashkov what OS are you using?

(It seems that we are experiencing different issues yes)

[rashkov]

I'm using Linux. You mentioned earlier that maybe it's an fsevents issue. From what I understand, watchify uses chokidar to watch for file changes, and chokidar uses fsevents to make that work on OS X systems. You might want to try to npm install chokidar and then run something like this, and then try saving your file to see if it picks up on that change. Make sure to change "./a.js" to the file that you're editing, of course.

var chokidar = require('chokidar');

chokidar.watch('./a.js').on('change', function(){
  console.log('changed');
});

[TylerK]

I'm also having the same issue as @franleplant

• OSX 10.10.3
• Node 0.12.2
• NPM 2.7.5
• Watchify 3.1.1
• SublimeText 3

When files are saved they're successfully kicking off my linters and other watch processes, but not Watchify.

[franleplant]

@rashkov run the test that you suggested and editing a.js file with vim triggers the change event.

[zertosh]

I spent the day fixing other thing so I haven't had a chance to test out what I'm about to suggest:

w.r.t. the editor and the change event: If your editor isn't doing an "edit" but rather an "alternate-save-then-rename" (vim's swap file, or sublime's "atomic_save"), then I'm not entirely sure that chokidar fires a "change" event. maybe that's considered an "unlink" followed by an "add"?

w.r.t. fsevents, have you tried watchify's "poll" option? that switches chokidar into polling mode, which IIUC does not use fsevents.

w.r.t. other watchers working, #201 (comment) might offer some clues.

[DavidStrada]

I don't know if I was having the same problem but i solve mine by replacing -o and use instead --outfile
( pasted my config below ).

watchify app/app.js -t babelify --outfile bundle.js --debug --verbose