I've tested the new command but got an error:
https://travis-ci.org/gr2m/semantic-release-cli-test#L564

It looks like it cannot access NPM_TOKEN but it is set at https://travis-ci.org/gr2m/semantic-release-cli-test#L422

I'll look more into it

I don't think it's the access to the environment variable, but the location of the .npmrc file

@pvdlg by the way the %O placeholder doesn't get replaced correctly: https://travis-ci.org/gr2m/semantic-release-cli-test#L564, I don't know why, works for me when testing locally with Node 8

> console.error('test 12 %O', new Error('funky'))
test 12 Error: funky
    at repl:1:29
    at ContextifyScript.Script.runInThisContext (vm.js:50:33)
    at REPLServer.defaultEval (repl.js:240:29)
    at bound (domain.js:301:14)
    at REPLServer.runBound [as eval] (domain.js:314:12)
    at REPLServer.onLine (repl.js:441:10)
    at emitOne (events.js:120:20)
    at REPLServer.emit (events.js:210:7)
    at REPLServer.Interface._onLine (readline.js:282:10)
    at REPLServer.Interface._line (readline.js:631:8)

But it doesn't when running in Node 6 or 4. Maybe the execa is messing with the npx command somehow?

Yes I noticed that as well. I'm looking at it.

On a local project if I run npx -p node@8 -c "semantic-release"
I get the error: /bin/sh: semantic-release: command not found

If I have semantic-release installed globally it works.

I'm really confused by what npx -p node@8 -c "semantic-release" actually does...
The problem with the NPM_TOKEN missing might be due to semantic-release not being executed from the root directory of the project...

Running on Node 8:

node -e "console.log('TEST %O', {a: 1})"
=> TEST { a: 1 }

npx -p node@8 -c "node -e \"console.log('TEST %O', {a: 1})\""
=> TEST %O { a: 1 }

¯_(ツ)_/¯

Ok the %O problem is due to nodejs/node#14558 that has been implemented in Node 8.4.0.

When running npx -p node@8 the version used is 8.3.0 as it's the latests published on npm.

So we can either decide to support only node >=8.4.0 or I'll have to find another way to format objects in logs. I'm sure their library that can do that.

I'm okay with supporting only Node >=8.9 as it became LTS today 🎉

npx -p node@8 -c "node -e "console.log('TEST %O', {a: 1})""
=> TEST %O { a: 1 }

I was not able to reproduce this ¯\_(ツ)_/¯

My guess it had an older Node 8 version installed and because it matched the wanted node version it used the local version instead of getting the latest? Try

npx -p node@8.9.0 -c "node -e \"console.log('TEST %O', {a: 1})\""

by the way node is just an npm package: https://www.npmjs.com/package/node. So npx installs the node package and runs the command string against its binary, I guess

I get the error: /bin/sh: semantic-release: command not found

can you try the --shell-auto-fallback flag?

Docs say

--shell-auto-fallback [] - Generates shell code to override your shell's "command not found" handler with one that calls npx. Tries to figure out your shell, or you can pass its name (either bash, fish, or zsh) as an option. See below for how to install.

I was not able to reproduce this ¯_(ツ)_/¯

It happens with node <= 8.4.0
So npx -p node@8.3.0 -c "node -e "console.log('TEST %O', {a: 1})"" would create the problem with %O.
Since today the last of node@8 release on npm is 8.9.0, so npx -p node@8 works.

can you try the --shell-auto-fallback flag?

Now running npx -p node@8 -c "semantic-release" works... I don't have /bin/sh: semantic-release: command not found

Maybe a weird bug somewhere between a specific version of node / npx / npm?

Fixed by #593