Alex Early
Alex Early
Here's a use case that fails for me, that might be what @chrisabrams is describing: ``` watchify test/*.test.js -o public/js/tests.js -v ``` This will build the current set of test...
I just came across [fireworm](https://github.com/airportyh/fireworm) which can watch globs patterns for new files (as well as the other standard `fs.watch` events). It needs a `basedir` to start from, however.
@simonzack the issue is glob expansion before the list of files is handed to watchify. `watchify test/*.test.js -o public/js/tests.js` gets expanded to: `watchify test/foo.test.js test/bar.test.js test/baz.test.js -o public/js/tests.js` and then...
Yep, or probably something like `watchify --entry-glob 'test/*.test.js' -o public/js/tests.js` to make it explicit.
:+1: for examples
I cannot reproduce this. Make sure your typescript/babel/esbuild/etc. compiler is targeting ES2017 or later and preserving `async` functions. ``` ❯ node async.js item: a secondItem: c secondItem: d item: b...
Workaround: https://github.com/bermi/sauce-connect-launcher/issues/26#issuecomment-44104784
Also, later versions of sauce-connect-launcher don't try to download sauce-connect on `npm install` anymore
This is expected behavior. The first `async` function is implicitly returning `undefined`, so that is the return value passed to the next function. We can't detect the difference between an...
I've noticed the same thing too, culprit was this extension. KiTTY was another app that showed this un-maximizing behavior.