David is React
The David website has been rewritten to use React and Redux and both server and client are now written using ES2015 syntax and features. Yay! You should hopefully notice a performance improvement as you navigate around the site.
noise dept.

★
Keni

Discoholic 🪩

PR's Tumblrdome
Show & Tell

Andulka

#extradirty

祝日 / Permanent Vacation
Misplaced Lens Cap
Game of Thrones Daily
Three Goblin Art
No title available
ojovivo
Stranger Things

izzy's playlists!
Not today Justin
Mike Driver
Peter Solarz
Aqua Utopia|海の底で記憶を紡ぐ
seen from United States

seen from United States

seen from Malaysia
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from France

seen from United States
seen from Germany
seen from United States
seen from United States

seen from France
seen from Brazil
seen from United States
seen from Indonesia

seen from Romania

seen from United States

seen from Bosnia & Herzegovina
@davidiswatching
David is React
The David website has been rewritten to use React and Redux and both server and client are now written using ES2015 syntax and features. Yay! You should hopefully notice a performance improvement as you navigate around the site.
Non-root package.json
A long time coming, but david-dm.org now supports projects that don’t have their package.json in the root directory. It means that if you can put your package.json wherever your like within your repo and can even have multiple package.json files if you’re that way inclined.
How do you access this magic? Simply add a `?path=` to your status page or badge URL.
For example:
https://david-dm.org/alanshaw/non-root-package.json?path=src https://david-dm.org/alanshaw/non-root-package.json?path=src/test
Branches and tags
Thanks to @aivus, branches and tags are now supported when viewing status pages or badges. Simply add your branch name to the end of your status page URL or badge URL (before the file extension) to see dependency status for that branch or tag.
Private repos
David now supports viewing status pages for private github repos. Login to github using the link in the top left and you'll be able to view status pages for all the private repos you have access to.
Flat syle badges
You can now display flat style badges on your repo, simply add ?style=flat to your existing badge image URLs.
You can also visit your project status page on david-dm.org, click on your badge in the top right and select "Flat" from the dropdown.
The flat badges recently appeared on http://shields.io/ (bottom of the page) and look awesome!
Peer and optional dependencies support
David now supports peer and optional dependencies. On your project status page you'll now see tabs for peerDependencies and optionalDependencies (if you project has peer or optional dependencies). You can view your dependencies in list or graph view as you can with regular and devDependencies. You can also get badges for peer and optional dependencies by clicking on the badge in the top right.
shields.io badges
David now has shields.io badges you can embed on your github readme/blog/whatever. Shields.io make legible, concise & consistent badges. You can read more about them on their github page.
Here's the status badge for mikeal's request module using the shields.io theme:
Changelog
Visibility of what has changed between the version your project depends on and the latest module version is usually low unless the module author has made some effort to document the changes they make to a project in a changelog or by some other means. Good news, David makes this a little easier for you.
If you project has an out of date dependency you'll now see a new icon next to it on your status page. Clicking this icon will get a list of closed issues and commits that were made to the repository between the date the module version your project depends on was released and the date the latest stable version of the module was released.
This feature is experimental so please send us some feedback if you have any ideas or questions. It's limited to just public GitHub repositories and requires that the module author has added a "repositories" section to their package.json with a valid Git URL.
Retina badges
David now has retina badges. A retina badge URL is the badge URL with “@2x” appended to the end of the badge filename. For example, the retina badge for bower is at https://david-dm.org/bower/[email protected]
Check it out:
Cached package.json auto expiry
David now automatically expires its cached version of your package.json file when you publish to NPM. This means that if you have updated your dependencies, your badge and status page on david-dm.org will update almost as soon as you have published.
David does this by using couchwatch to listen for changes to the NPM registry. Super thanks to @mikeal for the suggestion and gist
Update from CLI
David v1.8.0 can update your project dependencies to the latest stable versions from the command line. It'll also update your package.json file with the new version numbers.
All you need to do is install david globally using
npm install david -g
and then run
david update
from your project directory.
Visual NPM search
David has a new feature: Visual NPM search. The new search page shows your search results in a d3 bubble graph. What's interesting about this is that the size and colour of the bubble represents the popularity of the module.
Popularity is determined by how many projects David knows about that use the module.
This should go some way to giving you an idea of how easy to use, well maintained and secure the module is by virtue of how many people have decided it is good enough to be used in their projects.
The new search page can be found here: https://david-dm.org/search
Here's some interesting searches:
https://david-dm.org/search?q=glob https://david-dm.org/search?q=request https://david-dm.org/search?q=async
New Clothes!
David has some new clothes and looks smarter than ever! Seriously though, the site look and feel has changed but everything should be more or less where you left it before. If you find something broken or missing, please open a ticket.
Badges for devDependencies
David recently added support for viewing a project's devDependencies status. Yesterday David was updated with the final piece in the puzzle - you can now embed a badge that shows your project's devDependency status.
On a project status page, click on the devDependencies tab - you'll notice the badge at the top changes. Click on the changed badge to get the embed code.
Here's the devDependencies badge for david:
Experimental RSS
RSS feeds have landed. They're showing a list of dependency version updates specific to your project. What this means is that if you depend on xxx ~0.1.1 and yyy ~2.7.2 you'll see something like this in your RSS feed when they're updated:
xxx 0.1.1 to 0.1.2 (~0.1.1 required) 22 February 2013 11:44
yyy 2.7.2 to 2.7.3 (~2.7.3 required) 19 February 2013 23:50
e.g. https://david-dm.org/visionmedia/express/rss.xml
There'll be improvements in the coming weeks but for now, enjoy :)
Watching your devDependencies
You can now see dependency status for your project devDependencies. For example: https://david-dm.org/yeoman/yo#info=devDependencies
This was a relatively easy change in terms of the david module, but was a lot trickier to implement in the frontend. David only wants to load the dependency data upfront and load everything else via AJAX as required. Since the graph data for the tree view is already loaded on demand it was fiddly to also load another set of dependency data, display it, and potentially load another set of graph data for the tree view whilst maintaining state on the window.location.hash so that the correct tab and view could be copied and pasted from the browser URL bar and the recipient open the URL at the correct dataset and view. Phew.
Anyway, david nailed it.
d3 project dependency tree view
David has a new feature that'll show your project dependencies in a tree view. It uses d3js.org and it looks amazing.
The view is interactive, so you can click on a dependency and the graph will expand out to show the packages it depends on (if any).
Here's an example.
You can view the tree view for any project by clicking on the tree icon, to the top right of the dependency list on your project status page.
Enjoy!