Build script fails: proxies not supported on this platform

Description

After I clone the git repo, I run script/bootstrap and then script/build which fails with the following error message: proxies not supported on this platform. On v8/node/iojs, make sure to pass the --harmony_proxies flag.

Tell us a bit about yourself:

• Version of JekyllAdmin I’m using: 0.5.1
• Version of Jekyll I’m using: 3.4.3
• Version of NodeJS I’m using: 4.2.6
• Operating System: Ubuntu 16.04

Steps to reproduce:

1. git clone [e-mail]:fowlie/jekyll-admin.git
2. cd jekyll-admin
3. script/bootstrap
4. script/build

Other details:

jekyll-admin/npm-debug.log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs',
1 verbose cli   '/usr/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build',
1 verbose cli   '--harmony_proxies' ]
2 info using npm@3.5.2
3 info using node@v4.2.6
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle jekyll-admin@0.5.1~prebuild: jekyll-admin@0.5.1
6 verbose lifecycle jekyll-admin@0.5.1~prebuild: unsafe-perm in lifecycle true
7 verbose lifecycle jekyll-admin@0.5.1~prebuild: PATH: /usr/share/npm/bin/node-gyp-bin:/home/matfau/dev/private/jekyll-admin/node_modules/.bin:/home/matfau/bin:/home/matfau/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/matfau/bin:/opt/java/bin:/opt/maven/bin:/home/matfau/.rvm/bin:/home/matfau/.rvm/bin
8 verbose lifecycle jekyll-admin@0.5.1~prebuild: CWD: /home/matfau/dev/private/jekyll-admin
9 silly lifecycle jekyll-admin@0.5.1~prebuild: Args: [ '-c',
9 silly lifecycle   'npm run clean-dist && npm run build:html && npm run lint && npm test' ]
10 silly lifecycle jekyll-admin@0.5.1~prebuild: Returned: code: 1  signal: null
11 info lifecycle jekyll-admin@0.5.1~prebuild: Failed to exec prebuild script
12 verbose stack Error: jekyll-admin@0.5.1 prebuild: `npm run clean-dist && npm run build:html && npm run lint && npm test`
12 verbose stack Exit status 1
12 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
12 verbose stack     at emitTwo (events.js:87:13)
12 verbose stack     at EventEmitter.emit (events.js:172:7)
12 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
12 verbose stack     at emitTwo (events.js:87:13)
12 verbose stack     at ChildProcess.emit (events.js:172:7)
12 verbose stack     at maybeClose (internal/child_process.js:821:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
13 verbose pkgid jekyll-admin@0.5.1
14 verbose cwd /home/matfau/dev/private/jekyll-admin
15 error Linux 4.4.0-78-generic
16 error argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build" "--harmony_proxies"
17 error node v4.2.6
18 error npm  v3.5.2
19 error code ELIFECYCLE
20 error jekyll-admin@0.5.1 prebuild: `npm run clean-dist && npm run build:html && npm run lint && npm test`
20 error Exit status 1
21 error Failed at the jekyll-admin@0.5.1 prebuild script 'npm run clean-dist && npm run build:html && npm run lint && npm test'.
21 error Make sure you have the latest version of node.js and npm installed.
21 error If you do, this is most likely a problem with the jekyll-admin package,
21 error not with npm itself.
21 error Tell the author that this fails on your system:
21 error     npm run clean-dist && npm run build:html && npm run lint && npm test
21 error You can get information on how to open an issue for this project with:
21 error     npm bugs jekyll-admin
21 error Or if that isn't available, you can get their info via:
21 error     npm owner ls jekyll-admin
21 error There is likely additional logging output above.
22 verbose exit [ 1, true ]

[ashmaroli]

What else could be different in my env?

I can’t think of any at the moment. Though I introduced those changes, I don’t know how I’d be able to “fix” them, since those tests pass as it is… For now I suggest that you ignore those failures and continue working on your contribution.

[jekyllbot]

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.