devDependencies bug introduced

I've recreated an issue I'm encountering after using the devDependencies release.

The issue is that once you pass in `dev: true` every subsequent list will return the dev dependencies even with `false` explicitly passed in.

The order of this test matters because it doesn't fail when `noDevDependencies` is run before the existing `devDependencies` test.