mike-north/ember-cli-materialize

Unable to install it (spawn undefined ENOENT)

jbruchanov opened this issue · 5 comments

f:\2Projects\web\ember-sample>node --version
v6.9.1

f:\2Projects\web\ember-sample>ember --version
ember-cli: 2.11.1
node: 6.9.1
os: win32 x64

f:\2Projects\web\ember-sample>ember install ember-cli-materialize
Installed packages for tooling via npm.
installing ember-cli-materialize
  install addons ember-composability@~0.3.7, ember-radio-button@1.0.7, ember-new-computed@~1.0.2, ember-keyboard@1.0.3, ember-truth-helpers@1.2.0, ember-modal-dialog@~0.8.0, ember-materialize-shim@~0.2.0
Installed packages for tooling via npm.
installing ember-materialize-shim
  install bower package materialize
  cached https://github.com/Dogfalo/materialize.git#0.97.6
  cached https://github.com/jquery/jquery-dist.git#3.1.1
Installed browser packages via Bower.
  install addons ember-cli-sass@~5.3.0, ember-material-design-icons-shim@~0.1.9
Installed packages for tooling via npm.
Installed addon package.
  install package node-sass@~3.4.0
#COMMENT - it's red from this point
spawn undefined ENOENT
> node-sass@3.13.1 install f:\2Projects\web\ember-sample\node_modules\broccoli-sass-source-maps\node_modules\node-sass
> node scripts/install.js

Cached binary found at C:\Users\Scurab\AppData\Roaming\npm-cache\node-sass\3.13.1\win32-x64-48_binding.node

> node-sass@3.4.2 install f:\2Projects\web\ember-sample\node_modules\node-sass
> node scripts/install.js


> node-sass@3.13.1 postinstall f:\2Projects\web\ember-sample\node_modules\broccoli-sass-source-maps\node_modules\node-sass
> node scripts/build.js

Binary found at f:\2Projects\web\ember-sample\node_modules\broccoli-sass-source-maps\node_modules\node-sass\vendor\win32-x64-48\binding.node
Testing binary
Binary is fine

> node-sass@3.4.2 postinstall f:\2Projects\web\ember-sample\node_modules\node-sass
> node scripts/build.js

Building: C:\Program Files\nodejs\node.exe f:\2Projects\web\ember-sample\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
glob@7.1.1 node_modules\node-sass\node_modules\glob -> node_modules\broccoli-sass-source-maps\node_modules\glob
lodash.assign@4.2.0 node_modules\node-sass\node_modules\lodash.assign -> node_modules\broccoli-sass-source-maps\node_modules\lodash.assign
ember-sample@0.0.0 f:\2Projects\web\ember-sample
`-- ember-cli-sass@5.3.1
  `-- broccoli-sass-source-maps@1.8.1
    `-- node-sass@3.13.1
      +-- cross-spawn@3.0.1
      +-- gaze@1.1.2
      | `-- globule@1.1.0
      |   `-- lodash@4.16.6
      `-- mkdirp@0.5.1

any ideas ?

have the same problem

PS D:\Cordova\material> ember --version
ember-cli: 2.14.1
node: 6.9.5
os: win32 x64

> node-sass@3.4.2 postinstall D:\Cordova\material\node_modules\node-sass
> node scripts/build.js

Building: C:\Program Files\nodejs\node.exe D:\Cordova\material\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
glob@7.1.2 node_modules\node-sass\node_modules\glob -> node_modules\broccoli-sass-source-maps\node_modules\glob
lodash.assign@4.2.0 node_modules\node-sass\node_modules\lodash.assign -> node_modules\broccoli-sass-source-maps\node_modules\lodash.assign
material@0.0.0 D:\Cordova\material
`-- ember-cli-sass@5.3.1
  `-- broccoli-sass-source-maps@1.8.1
    `-- node-sass@3.13.1
      +-- cross-spawn@3.0.1
      +-- gaze@1.1.2
      | `-- globule@1.2.0
      `-- mkdirp@0.5.1


    at Promise.all.then.arr (D:\Cordova\material\node_modules\execa\index.js:210:11)
    at process._tickCallback (internal/process/next_tick.js:103:7)

Also I've noticed some errors in npm-debug.log

6788 verbose stack Error: EPERM: operation not permitted, rename 'D:\Cordova\material\node_modules\node-sass' -> 'D:\Cordova\material\node_modules\.node-sass.DELETE'

both 'D:\Cordova\material\node_modules\node-sass' and 'D:\Cordova\material\node_modules.node-sass.DELETE' folders exists

full log is attached
npm-debug.zip

I suspect that this may be related to ember-cli-materialize pulling in ember-cli-release which pins npm to an old version. See shipshapecode/ember-cli-release#63 & shipshapecode/ember-cli-release#69 It's also possible that it's a Windows file permissions problem.

@romandubrov I realize this is an old issue (I just recently started collaborating on this project and we have a lot of catch-up to do), but I wanted to ask you:

  1. Are you still having this problem? / Were you able to resolve this problem?
  2. Did you try following npm's recommendation at the end of the log?

    Please try running this command again as root/Administrator.

@jacobq unfortunately I can't test it anymore as I decided not to use ember + materialize due to this issue.

@romandubrov Thanks for replying. I completely understand and am sorry that you were not able to get it working. I am going to close this issue due to inactivity / irrelevance then. Hopefully upcoming improvements will help others avoid this.