Atom Erroneously Rejects Package For DevDependency That Isn't Binary Compatible

[seflless]

Hi.

Since upgrading atom I've had to remove certain modules it seems because of binary incompatibility. Which is all fine. But I use gulp-watch which isn't used in my packages run-time, just for a development workflow. What am I doing wrong? Or is this expected? It seems not being able to use any tool you want during development is a major limitation.

My Package .json when it doesn't work and I get the above error:

{
  "name": "jibo-atom",
  "main": "./lib/main",
  "version": "1.0.1",
  "description": "Example package to open any HTML in a tab.",
  "repository": "ssh://git@git.jibo.com:7999/sdk/jibo-atom.git",
  "license": "MIT",
  "engines": {
    "atom": ">0.170.0"
  },
  "dependencies": {
    "URIjs": "^1.15.0",
    "animationcontent": "git+ssh://git@git.jibo.com:7999/spc/animationcontent.git",
    "animationutilities": "git+ssh://git@git.jibo.com:7999/spc/animationutilities.git",
    "atom-pane": "^1.0.1",
    "atom-space-pen-views": "^2.0.5",
    "basebehaviors": "git+ssh://git@git.jibo.com:7999/spc/basebehaviors.git",
    "clamp": "^1.0.1",
    "dof-controller": "git+ssh://git@git.jibo.com:7999/spc/dof-controller.git",
    "jibo-tools": "git+ssh://git@github.jibo.com:sdk/jibo-tools.git",
    "jquery": "^2.1.3",
    "keyframes-runtime": "git+ssh://git@github.jibo.com:sdk/keyframes-runtime.git",
    "lodash": "^3.7.0",
    "mkdirp": "^0.5.0",
    "npm": "^2.8.4",
    "object-assign": "^2.0.0",
    "react": "^0.13.1",
    "space-pen": "^5.1.1",
    "sub-atom": "1.0.x",
    "theorist": "1.0.2",
    "three": "^0.70.0",
    "wrench": "^1.5.8"
  },
  "devDependencies": {
    "gulp": "^3.8.11",
    "gulp-babel": "^4.0.1",
    "gulp-cached": "^1.0.4",
    "gulp-coffee": "^2.3.1",
    "gulp-sourcemaps": "^1.5.1",
    "gulp-watch": "^4.2.4"
  }
}

Just removing gulp-watch from the devDependencies makes it all work again:

{
  "name": "jibo-atom",
  "main": "./lib/main",
  "version": "1.0.1",
  "description": "Example package to open any HTML in a tab.",
  "repository": "ssh://git@git.jibo.com:7999/sdk/jibo-atom.git",
  "license": "MIT",
  "engines": {
    "atom": ">0.170.0"
  },
  "dependencies": {
    "URIjs": "^1.15.0",
    "animationcontent": "git+ssh://git@git.jibo.com:7999/spc/animationcontent.git",
    "animationutilities": "git+ssh://git@git.jibo.com:7999/spc/animationutilities.git",
    "atom-pane": "^1.0.1",
    "atom-space-pen-views": "^2.0.5",
    "basebehaviors": "git+ssh://git@git.jibo.com:7999/spc/basebehaviors.git",
    "clamp": "^1.0.1",
    "dof-controller": "git+ssh://git@git.jibo.com:7999/spc/dof-controller.git",
    "jibo-tools": "git+ssh://git@github.jibo.com:sdk/jibo-tools.git",
    "jquery": "^2.1.3",
    "keyframes-runtime": "git+ssh://git@github.jibo.com:sdk/keyframes-runtime.git",
    "lodash": "^3.7.0",
    "mkdirp": "^0.5.0",
    "npm": "^2.8.4",
    "object-assign": "^2.0.0",
    "react": "^0.13.1",
    "space-pen": "^5.1.1",
    "sub-atom": "1.0.x",
    "theorist": "1.0.2",
    "three": "^0.70.0",
    "wrench": "^1.5.8"
  },
  "devDependencies": {
    "gulp": "^3.8.11",
    "gulp-babel": "^4.0.1",
    "gulp-cached": "^1.0.4",
    "gulp-coffee": "^2.3.1",
    "gulp-sourcemaps": "^1.5.1"
  }
}

[bripkens]

I am having the same issue with the project-sidebar package. Babel is included as a devDependency.

Listed below are the incompatible native modules that this package depends on.
fsevents@0.3.6
Error message: Module version mismatch. Expected 43, got 14.

Excerpt from package.json:

"dependencies": {
    "lodash": "^3.9.1",
    "react": "^0.13.3",
    "season": "^5.2.0"
  },
  "devDependencies": {
    "babel": "^5.4.4"
  }

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!