iron-node profiling fails with multiple errors

[radiovisual]

Description

When following the profiling instructions in maintaining.md:

$ iron-node node_modules/ava/profile.js <test-file>

I get multiple runtime errors (see below). If it helps, I ran the profiler against the AVA tests in https://github.com/sindresorhus/generator-nm

Error Message & Stack Trace

Here is the text from the screenshot above:

ironNode boot
/usr/local/lib/node_modules/iron-node/app/require-custom-wrap.js:32 Object {v8: Object, app: Object}
Profile 'AVA test-worker process' started.
media/header.png:1 GET file:///usr/local/lib/node_modules/iron-node/app/media/header.png net::ERR_FILE_NOT_FOUND
media/screenshot-mini-reporter.gif:1 GET file:///usr/local/lib/node_modules/iron-node/app/media/screenshot-mini-reporter.gif net::ERR_FILE_NOT_FOUND
common.js:42 exec: internal errorlog @ common.js:42error @ common.js:70_exec @ exec.js:266(anonymous function) @ common.js:275user.git.name @ user.js:30prompt.then.props @ index.js:88
app.js:58   TypeError: Cannot read property 'stdout' of null
  
  - user.js:30 Object.user.git.name
    [generator-nm]/[yeoman-generator]/lib/actions/user.js:30:70
  
  - index.js:88 prompt.then.props
    /Users/michael/forks/generator-nm/app/index.js:88:25
  
error @ app.js:58emitOne @ events.js:101emit @ events.js:188processEmit @ index.js:146window.onerror @ init.js:114
app.js:59 Details TypeError: Cannot read property 'stdout' of null(…)error @ app.js:59emitOne @ events.js:101emit @ events.js:188processEmit @ index.js:146window.onerror @ init.js:114
profile.js:125 TypeError: Cannot read property 'stdout' of null
    Object.user.git.name (node_modules/yeoman-generator/lib/actions/user.js:30:70)
    prompt.then.props (app/index.js:88:25)

Environment

iron-node@3.0.11
Node.js: v4.4.4
darwin: 14.5.0
AVA: 0.15.2
npm: 2.15.1

(This issue is related to the archived issue #798)

[novemberborn]

I've never used iron-node. @avajs/core any ideas?

Is this something we should still include? Seems prone to breaking…

[sindresorhus]

Same answer as #989 (comment).

[novemberborn]

Could anybody confirm whether this is still an issue?