I have some problems with npm packages in my bundles.

1. I create a new meteor project, add a npm package (lodash for example) and use it in the client-only-side (client/ folder for example). Then I run meteor build. Wait (soooo many time). Open final archive and see /bundle/programs/server/npm/node_modules/. Among other things I see lodash folder. In the server area (!). What for?
2. I create a new meteor project, add a native (atmosphere) package (reywood:publish-composite for example). Then I run meteor build. Wait. Open final archive and see /bundle/programs/server/npm/node_modules/meteor/reywood_publish-composite/node_modules/. I see eslint folders. What for? Ok. Go to publish-composite github repository. Open the package.json. All eslint packages in devDependencies area. Why they in the production bundle?

All of this points make my bundles sooo big. And it's very bad, I think.

Examples at my github repo: https://github.com/JWo1F/meteor-npm-bugs

Meteor version: 1.6.1.
Operating System: Fedora 21.