apollo-errors Message not propagating in 1.7.1

Changes between versions 1.5.1 and 1.7.1 appear to have broken the message field propagation when using createError:

const myError = createError('BadError', { message: "This is bad"}); var theError = new myError(); console.log(theError.message)

output of message field is undefined....

Works great in 1.5.1, broken in 1.7.1

Feb 26 '18 16:02 prperrino

I am seeing the same thing. I don't know enough about the history and/or reasoning to use arguments[2] in the ApolloError constructor (instead of using the config variable) to put in a PR for it, but there are only 2 args in the arguments array when I through and the relevant data is in config / arguments[1].

I haven't tried v 1.5.1 myself, but by tweaking that argument reference it works as expected for me.

Feb 26 '18 18:02 azterix

Thanks! I'll try to submit a fix for this later tonight

Feb 26 '18 19:02 thebigredgeek

Somehow this only happens if I run it in production mode, locally it works?

Mar 01 '18 12:03 Ponjimon

Please, fix this )

Mar 02 '18 15:03 groundmuffin

I am attempting to throw an error inside of a resolver by doing throwing an error created using apollo-errors

const UserDoesntExistError = createError("UserDoesntExist", {
  message: "A user with this email address does not exist",
})
...
if (!user) throw new UserDoesntExistError()

On the frontend when this error occurs, the message is not displayed.