Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_INVALID_ARG_TYPE error for Node v10.5.0 #67

Open
arianseyedi opened this issue Jun 27, 2018 · 7 comments
Open

ERR_INVALID_ARG_TYPE error for Node v10.5.0 #67

arianseyedi opened this issue Jun 27, 2018 · 7 comments

Comments

@arianseyedi
Copy link

Hello,

I am trying to test parallelshell (package.json at the bottom of this issue for ref) simply running echo commands, but I get the following:

confusion@1.0.0 echo1echo2 C:\Users\Public\r\b\c
> parallelshell "echo 1" "echo 2"

child_process.js:420
throw new ERR_INVALID_ARG_TYPE('options.cwd', 'string', options.cwd);
^

TypeError [ERR_INVALID_ARG_TYPE]: The "options.cwd" property must be of type string. Received type function
at normalizeSpawnArguments (child_process.js:420:11)
at spawn (child_process.js:522:38)
at C:\Users\Public\repos\Bootstrap4\conFusion\node_modules\parallelshell\index.js:104:17
at Array.forEach ()
at Object. (C:\Users\Public\r\b\c\node_modules\parallelshell\index.js:100:6)
at Module._compile (internal/modules/cjs/loader.js:702:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
at Module.load (internal/modules/cjs/loader.js:612:32)
at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
at Function.Module._load (internal/modules/cjs/loader.js:543:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! confusion@1.0.0 echo1echo2: parallelshell "echo 1" "echo 2"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the confusion@1.0.0 echo1echo2 script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\username\appdata\Roaming\npm-cache_logs\2018-06-27T08_21_16_022Z-debug.log

The package I have installed in my project folder has the following package.json file:

{
"_from": "parallelshell",
"_id": "parallelshell@3.0.2",
"_inBundle": false,
"_integrity": "sha512-aW73W8tmYiFZtQi41pweV3WWT6o/EvSxAVQHbumOhN53H47OuWQwrRc11xQ2i44GFvR5AjtzhD92r8Kv9X+7Iw==",
"_location": "/parallelshell",
"_phantomChildren": {},
"_requested": {
"type": "tag",
"registry": true,
"raw": "parallelshell",
"name": "parallelshell",
"escapedName": "parallelshell",
"rawSpec": "",
"saveSpec": null,
"fetchSpec": "latest"
},
"_requiredBy": [
"#DEV:/",
"#USER"
],
"_resolved": "https://registry.npmjs.org/parallelshell/-/parallelshell-3.0.2.tgz",
"_shasum": "fffc55aaa145bdd44b5381cf7fd5e521fc21aa7b",
"_spec": "parallelshell",
"_where": "C:\Users\Public\repos\Bootstrap4\conFusion",
"author": {
"name": "DARKGuy",
"email": "darkguy2008@gmail.com"
},
"bin": {
"parallelshell": "./index.js"
},
"bugs": {
"url": "https://github.com/darkguy2008/parallelshell/issues"
},
"bundleDependencies": false,
"deprecated": false,
"description": "Invoke multiple commands, running in parallel",
"devDependencies": {
"bluebird": "^3.5.0",
"chai": "^4.0.2",
"coffee-script": "^1.12.6",
"mocha": "^3.4.2"
},
"homepage": "https://github.com/darkguy2008/parallelshell",
"keywords": [
"parallel",
"shell"
],
"license": "MIT",
"main": "index.js",
"name": "parallelshell",
"repository": {
"type": "git",
"url": "git+ssh://git@github.com/darkguy2008/parallelshell.git"
},
"scripts": {
"test": "mocha"
},
"version": "3.0.2"
}

Thank you so much. Sorry if I was all over the place or something. I'm new to this.

Arian

@alexander-schranz
Copy link

alexander-schranz commented Jul 4, 2018

@arianseyedi think this is related to this issue: #64 which I think is fixed but not released. ping @darkguy2008

Until its released you could change this: 527bf01 manually in your node_modules/parallelshell/index.js

@t-fritsch
Copy link

hello
as said here #57 by @powelmaja : downgrade to 3.0.1 can be another temporary fix until the official one is released to npm (will it be one day ?)

@alexander-schranz
Copy link

@tfritsch-km I currently switch to concurrently as this repo seems to be unmaintained. There was also some discussion from the old maintainer of parallelshell to merge all this task/parallel script repo's in one see mysticatea/npm-run-all#10 so there is a list of alternatives.

@t-fritsch
Copy link

thank you @alexander-schranz for the alternatives, I saw concurrently before installing parallelshell but thought that it was too complex for my needs. That being said, my needs have evolved, and given the inactivity on this repo, I'll give it a try.

hkniberg added a commit to sveasmart/meter that referenced this issue Oct 11, 2018
thornjad added a commit to remotestorage/website that referenced this issue Oct 3, 2019
As far as I can tell and test, concurrently works as a drop-in
replacement here. Parallelshell does not appear to be maintained and the
npm-published version suffers from a critical bug which causes it to
fail on Node 10 and
above (darkguy2008/parallelshell#67).
@abhijithchowdary2
Copy link

Have we got solution for the error of parallelshell??

@alexander-schranz
Copy link

@abhijithchowdary2 this package is I think not longer maintained as you see last release 2017. I would switch to alternative. As written above I did switch to concurrently which seems still be maintained: https://github.com/kimmobrunfeldt/concurrently

@abhijithchowdary2
Copy link

abhijithchowdary2 commented May 28, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants