ionic-cli: TypeError: Cannot read property 'pipesCount' of undefined

From @unipheas on May 31, 2017 7:37

Ionic version: (check one with “x”) [ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1) [ ] 2.x [x] 3.x

I’m submitting a … (check one with “x”) [x] bug report [ ] feature request [ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/

Current behavior: I created a new app, installed my platforms, linked the app, ran resources, then tried to do ‘ionic upload’. It’s giving me an error of '_stream_readable.js:545 switch (state.pipesCount) { TypeError: Cannot read property ‘pipesCount’ of undefined …

Expected behavior: Successfully upload to Ionic Services

Steps to reproduce:

Related code:

_stream_readable.js:545
  switch (state.pipesCount) {
               ^

TypeError: Cannot read property 'pipesCount' of undefined
    at module.exports.Readable.pipe (_stream_readable.js:545:16)
    at module.exports.ZipArchiveOutputStream._smartStream (/usr/local/lib/node_modules/ionic/node_modules/compress-commons/lib/archivers/zip/zip-archive-output-stream.js:184:11)
    at module.exports.ZipArchiveOutputStream._appendStream (/usr/local/lib/node_modules/ionic/node_modules/compress-commons/lib/archivers/zip/zip-archive-output-stream.js:96:20)
    at module.exports.ArchiveOutputStream.entry (/usr/local/lib/node_modules/ionic/node_modules/compress-commons/lib/archivers/archive-output-stream.js:88:10)
    at module.exports.ZipStream.entry (/usr/local/lib/node_modules/ionic/node_modules/zip-stream/index.js:138:49)
    at Zip.append (/usr/local/lib/node_modules/ionic/node_modules/archiver/lib/plugins/zip.js:53:15)
    at Archiver._moduleAppend (/usr/local/lib/node_modules/ionic/node_modules/archiver/lib/core.js:172:16)
    at Archiver._onQueueTask (/usr/local/lib/node_modules/ionic/node_modules/archiver/lib/core.js:370:8)
    at /usr/local/lib/node_modules/ionic/node_modules/async/dist/async.js:4045:9
    at process (/usr/local/lib/node_modules/ionic/node_modules/async/dist/async.js:2316:17)

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):

global packages:

    @ionic/cli-utils : 1.2.0
    Cordova CLI      : 7.0.1 
    Ionic CLI        : 3.2.0

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-cordova       : 1.2.1
    @ionic/cli-plugin-ionic-angular : 1.2.0
    Cordova Platforms               : android 6.2.3 ios 4.4.0
    Ionic Framework                 : ionic-angular 3.3.0

System:

    Node       : v8.0.0
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.2 Build version 8E2002 
    ios-deploy : 1.9.1 
    ios-sim    : 5.0.13

Copied from original issue: ionic-team/ionic#11872

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 19 (5 by maintainers)

Most upvoted comments

I too downgraded to LTS and it now works.

unipheas on Jun 1, 2017

Yep, node 8 has fixed it in 8.1.2+

imhoffd on Jul 10, 2017

Node 7.10 works fine for me, but I get this error with Node 8.

jdhiro on Jun 6, 2017

Yes, I upgraded to node v8.2.1 and it worked.

Niveshkrishna on Aug 9, 2017

They have a proposed pull for 8.1 here.

https://github.com/archiverjs/node-archiver/issues/236

unipheas on Jun 8, 2017

Thanks Dan. Didn’t know Travis was using 8. Will revert to LTS as suggested

On Thu, 1 Jun 2017 at 05:09, Dan Imhoff notifications@github.com wrote:

Thanks for making us aware. This looks like an issue with one of our dependencies: archiverjs/node-archiver#236 https://github.com/archiverjs/node-archiver/issues/236

We recommend Node 6 LTS for the time-being, as recommended in the readme.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ionic-team/ionic-cli/issues/2375#issuecomment-305287048, or mute the thread https://github.com/notifications/unsubscribe-auth/AG5tSNTJeDf--qL8_68d2rAhRl2btE-aks5r_brXgaJpZM4NrwQs .

lathonez on May 31, 2017

Thanks for making us aware. This looks like an issue with one of our dependencies: https://github.com/archiverjs/node-archiver/issues/236

We recommend Node 6 LTS for the time-being, as recommended in the readme.

imhoffd on May 31, 2017