Yarn: Bug. Yarn couldn't build package phantomjs. npm could.

Created on 13 Oct 2016 · 32Comments · Source: yarnpkg/yarn

I tried to build this project Github, npm installed all node_modules without errors. But when I tried to do this with Yarn I have got error.
os Archliux 64bit
node v6.7.0
yarn v0.15.1

Building fresh packages... [1/6] ⠁ gifsicle [2/6] ⠁ jpegtran-bin [3/6] ⠁ optipng-bin [6/6] ⠁ phantomjs error /usr/share/nginx/html/123/Travel-Site-Test/node_modules/phantomjs: Command failed. Exit code: 1 Command: sh Arguments: -c node install.js Directory: /usr/share/nginx/html/123/Travel-Site-Test/node_modules/phantomjs Output: PhantomJS not found on PATH Phantom installation failed TypeError: Path must be a string. Received undefined at assertPath (path.js:7:11) at Object.join (path.js:1213:7) at findSuitableTempDirectory (/usr/share/nginx/html/123/Travel-Site-Test/node_modules/phantomjs/install.js:127:30) at /usr/share/nginx/html/123/Travel-Site-Test/node_modules/phantomjs/install.js:476:19 at nextTickCallback (/usr/share/nginx/html/123/Travel-Site-Test/node_modules/kew/kew.js:47:28) at _combinedTickCallback (internal/process/next_tick.js:67:7) at process._tickCallback (internal/process/next_tick.js:98:9) TypeError: Path must be a string. Received undefined at assertPath (path.js:7:11) at Object.join (path.js:1213:7) at findSuitableTempDirectory (/usr/share/nginx/html/123/Travel-Site-Test/node_modules/phantomjs/install.js:127:30) at /usr/share/nginx/html/123/Travel-Site-Test/node_modules/phantomjs/install.js:476:19 at nextTickCallback (/usr/share/nginx/html/123/Travel-Site-Test/node_modules/kew/kew.js:47:28) at _combinedTickCallback (internal/process/next_tick.js:67:7) at process._tickCallback (internal/process/next_tick.js:98:9) at SpawnError (/usr/lib/node_modules/yarn/lib/errors.js:18:1) at ChildProcess.proc.on.code (/usr/lib/node_modules/yarn/lib/util/child.js:107:15) at emitTwo (events.js:106:13) at ChildProcess.emit (events.js:191:7) at maybeClose (internal/child_process.js:877:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

Source

sonarct

👍21

Most helpful comment

Having the issue.
yarn v.0.19.1

"devDependencies": {
  ...  
  "karma-phantomjs-launcher": "1.0.2",
  "phantomjs": "2.1.7"
}

yarn --no-bin-links

PhantomJS not found on PATH
Phantom installation failed [TypeError: Path must be a string. Received undefined] TypeError: Path must be a string. Received undefined

mazavr on 9 Feb 2017

👍21

All 32 comments

I think i opened a similar issue: https://github.com/yarnpkg/yarn/issues/1015

jaygarcia on 13 Oct 2016

Looks like a dupe of #987, which also mentions a failed PhantomJS installation. (#1015 mentioned above was closed as a dupe of the same ticket).

markstos on 13 Oct 2016

It is not exactly duplicate. They fixed it in stringstream, but it still does not work in PhantomJS. I would reopen it.

igorshubovych on 9 Nov 2016

@igorshubovych did you try phantomjs-prebuilt instead (which is the latest version of phantomjs)? I wonder if the old phantomjs package was itself buggy, but npm happened to work with it.

markstos on 9 Nov 2016

Updating phantomjs-prebuilt to v2.1.8 fixed the problem for me.

noherczeg on 2 Jan 2017

👍11

I can reproduce the issue.
I have [email protected] and [email protected].

When I run yarn install I get the following error:

error /media/willem/DATA/Projects/Essent/service-api/node_modules/phantomjs: Command failed
...
Output
PhantomJS not found on PATH
Phantom installation failed TypeError: Path must be a string. Received undefined

With npm install PhantomJS installs fine.

Why was this issue closed?

hetzijzo on 3 Feb 2017

👍10

I'm having the same issue here.
I've already tried all solutions above.

estevaoam on 8 Feb 2017

Having the issue.
yarn v.0.19.1

"devDependencies": {
  ...  
  "karma-phantomjs-launcher": "1.0.2",
  "phantomjs": "2.1.7"
}

yarn --no-bin-links

PhantomJS not found on PATH
Phantom installation failed [TypeError: Path must be a string. Received undefined] TypeError: Path must be a string. Received undefined

mazavr on 9 Feb 2017

👍21

@markstos Can this be reopened? A few people have been experiencing this issue after #987 was closed. Thanks!

ilaif on 20 Feb 2017

👍3

@ilaif I don't have the ability to re-open it, but I'll mention @cpojer who does.

I still recommend using phantomjs-prebuilt instead (which is the latest version of phantomjs). With so many open issues, I could understand if the Yarn project chooses not to allocate resources fixing compatibility with an old, buggy package when yarn already works with the newer, recommended version of the package.

markstos on 22 Feb 2017

seeing this in [email protected] also

sixinli on 24 Feb 2017

@markstos this is not an issue with the old package only. I can reproduce this with yarn 0.20.3 and phantomjs-prebuilt 2.1.14.

However, this is only reproducible under Linux. On Windows 7 under Cygwin it works fine.

@cpojer please consider reopening this as it clearly isn't resolved. A lot of build environments depend on phantomjs for testing etc, so this is a major blocker for using Yarn in them.

csvan on 28 Feb 2017

@csvan Could you post the output of your failure to build phantomjs-prebuilt on Linux?

markstos on 28 Feb 2017

@markstos Good day. There is no more problem with yarn and package phantomjs-prebuilt. I installed it successfully just now.
OS: Arch Linux 4.9.9-1
nodejs: v7.5.0
yarn: v0.21.3

Thanks to all

xm@localhost:http/testtest $ yarn add phantomjs-prebuilt yarn add v0.21.3 info No lockfile found. [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... [4/4] Building fresh packages... success Saved lockfile. success Saved 90 new dependencies.

sonarct on 28 Feb 2017

@markstos getting this on CentOS 7 when running yarn install in a project with "phantomjs-prebuilt": "^2.1.14" as a dep. Using Node 6.9.5. and Yarn 0.20.3:

[INFO] [4/4] Building fresh packages...
[ERROR] error /opt/balthazar/workdir/web/node_modules/phantomjs: Command failed.
[ERROR] Exit code: 1
[ERROR] Command: sh
[ERROR] Arguments: -c node install.js
[ERROR] Directory: /opt/balthazar/workdir/web/node_modules/phantomjs
[ERROR] Output:
[ERROR] PhantomJS not found on PATH
[ERROR] Phantom installation failed TypeError: Path must be a string. Received undefined
[ERROR]     at assertPath (path.js:7:11)
[ERROR]     at Object.join (path.js:1211:7)
[ERROR]     at findSuitableTempDirectory (/opt/balthazar/workdir/web/node_modules/phantomjs/install.js:127:30)
[ERROR]     at /opt/balthazar/workdir/web/node_modules/phantomjs/install.js:476:19
[ERROR]     at nextTickCallback (/opt/balthazar/workdir/web/node_modules/kew/kew.js:47:28)
[ERROR]     at _combinedTickCallback (internal/process/next_tick.js:67:7)
[ERROR]     at process._tickCallback (internal/process/next_tick.js:98:9) TypeError: Path must be a string. Received undefined
[ERROR]     at assertPath (path.js:7:11)
[ERROR]     at Object.join (path.js:1211:7)
[ERROR]     at findSuitableTempDirectory (/opt/balthazar/workdir/web/node_modules/phantomjs/install.js:127:30)
[ERROR]     at /opt/balthazar/workdir/web/node_modules/phantomjs/install.js:476:19
[ERROR]     at nextTickCallback (/opt/balthazar/workdir/web/node_modules/kew/kew.js:47:28)
[ERROR]     at _combinedTickCallback (internal/process/next_tick.js:67:7)
[ERROR]     at process._tickCallback (internal/process/next_tick.js:98:9)
[INFO] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

csvan on 28 Feb 2017

@csvan Your failure is in "findSuitableTempDirectory". You apparently don't have permission to write to several possible temp directories on your system. See:

https://github.com/Medium/phantomjs/blob/master/install.js#L105

That appears to be your problem, not yarns. Try again after setting your own environment variable to a working value: npm_config_tmp=/some/tmp/dir/you/can/actually/write/to yarn install.

I used yarn to install phantomjs-prebuilt without problems (on Ubuntu Linux).

markstos on 28 Feb 2017

👍8

@markstos great catch, I will try that. Does NPM do this by default? The above project builds fine with NPM 3.10, it only fails under Yarn.

csvan on 28 Feb 2017

@markstos nvm, just noticed NPM does set this var whereas Yarn doesn't. My problem is thus actually this issue: https://github.com/yarnpkg/yarn/issues/1538. Thanks for your help!

csvan on 28 Feb 2017

👍1

This toolset works for me

node: v6.9.4
yarn: 0.21.3

"karma-phantomjs-launcher": "^1.0.2",
"phantomjs-prebuilt": "2.1.8",

the-teacher on 13 Mar 2017

It looks like this has been fixed in phantomjs-prebuilt v2.1.8 via Medium/phantomjs@5e6598f.

(If you're finding this bug because you're using prerender-spa-plugin, that package has an open issue to upgrade from phantomjs-prebuilt v2.1.7 where it's currently stuck due to a Windows problem -- see chrisvfritz/prerender-spa-plugin#36.)

dcecile on 4 May 2017

If you switch over to phantomjs-prebuilt to solve this problem, you then can't run it in an Alpine based docker container as it's not built for musl... so you also have to change your Linux distro... or make a custom build of phantom

mikestead on 6 Jun 2017

For anyone still having this issue, I recommend switching over to Chrome Headless. It does everything phantom does better, and is actively supported across all platforms.

csvan on 17 Jun 2017

👎4 👍1

@mikestead How does that work? Do I have to remove the launcher?