Renée

yeah not sure about side effects either, might try using it in some more projects first

Well that got a lot more complex to support the scope stuff introduced by #79 :laughing: it looks like it works tho, will do a major bump for this to...

Will do this for browserify 17 if there are no complaints by then

calls to that argument would not be collected as dependencies of the file. I considered that but thought that it would be very rare. But the check could be tightened...

#79 implements a fast special case to ignore `require` calls inside browserified bundles, which I think is the most common situation.

I don't think browserify should support nonstandard features. You would not be able to use them anyway after bundling without first applying babel to the result, so you might as...

Note that most (all?) browserify packages now use [acorn-node](https://npmjs.com/package/acorn-node) which has support for the latest features, and will match Node syntax with parser plugins if necessary.

I believe this wasn't done yet because acorn-node@2 broke compatibility with some old node.js version. I'd like to fix that at some point (the point of acorn-node is to support...

The issue there is that detective doesn't support JSX or ES modules syntax. It should not be run on JSX or ES modules files in the first place.

This issue is not about a bug but an optimization. Implementing the optimization would only hide the issue you're describing, not fix it. It would pop back up the moment...