Andreas
Andreas
Okay. The stack trace above tells you where it comes from. Or just debug it if you want to know, https://github.com/byteclubfr/node-sync-files/blob/master/bin/sync-files.js#L120-L122
btw update-notifier is another package https://github.com/yeoman/update-notifier
@naholyr Hello, do you have any chance to look into this one?
This bug can be "disabled" by setting `--no-notify-update`
@wamoyo Yes, it's an `update-notifier` issue.
@graywithanA @artknight I recently had the exact same issue. So I developed my own glob based version. go check it, hope it helps [`sync-glob`](https://github.com/AndyOGo/node-sync-glob)
@muloka Also nice, I like the `transform` option. Though I miss `exclude` and `multiple sources` features (which `sync-glob` provides)...
@shaddyz @dotmagic @gregjacobs I recently had the exact same issue. So I developed my own glob based version. go check it, hope it helps [`sync-glob`](https://github.com/AndyOGo/node-sync-glob)
@shaddyz thanks, np. Yeah, I hope it solves it well^^
guess this is related https://github.com/webpack/webpack/issues/7499 Could be a problem with `sideEffects` of webpack treeshaking...