Javascript developers need to make a transition like php and others have to module based apps, where you import just the libraries you need.
With things like require its not like it would be difficult to role your own framework like you can with php and composer (+all the symfony / laravel modules)
That's what using Browserify with CommonJS modules accomplishes, and has wide adoption. ES6 also specifies a module system, but it remains to be seen how that gets used or when it becomes the norm.
Yes and no. Libraries like jQuery and Underscore are often the basis of new frameworks and have been solid for a while now.
Like in other languages there's some wait and see to adoption. Going all in on a project that's been on GitHub a month no matter how many stars is foolish. JS devs have to make their decisions this way.
Not remotely true with JavaScript. Something which got 2k stars on gitub this year might be on the way out in a year, and you'll be stuck figuring out whether it still works with the new version of d3.js, or on the newest Chrome... and if it doesn't you have to either move on or fix it yourself.