Error if dev dependency is also prod dependency

[jraede]

I just ran into a fringe-case bug we may want to look at. I originally installed colors as a dev dependency. Then, later, I realized I wanted it in production, so I installed it again as a normal dependency. Thus, the module was listed in both my devDependencies map and dependencies map. When I later pushed my app to heroku, the buildpack removed all dev dependencies, as it is supposed to, but in this case there happened to be a dev dependency that was also a prod dependency. Pulled my hair out for 10 minutes before I realized what was going on.

Thoughts on if this is even something to address?

[searls]

ugh that's no fun. thanks for reporting

On Mon, Apr 21, 2014 at 7:31 PM, Jason Raede notifications@github.comwrote:

I just ran into a fringe-case bug we may want to look at. I originally
installed colors as a dev dependency. Then, later, I realized I wanted it
in production, so I installed it again as a normal dependency. Thus, the
module was listed in both my devDependencies map and dependencies map.
When I later pushed my app to heroku, the buildpack removed all dev
dependencies, as it is supposed to, but in this case there happened to be a
dev dependency that was also a prod dependency. Pulled my hair out for 10
minutes before I realized what was going on.

Thoughts on if this is even something to address?

Reply to this email directly or view it on GitHubhttps://github.com//issues/17
.