feat: allow customizable error

[psibean]

Exposes the statusCode, message, and code parameters for the error initialization

This will fix issue #55

[davidgonmar]

Looks good to me. One thing I'd add is that, since you are changing the interface, to allow adding a factory function instead of the CsrfErrorConfig (one or the other). Something like:

export type CsrfErrorConfig = {
  statusCode: number;
  message: string;
  code: string | undefined;
} | {
  buildError: () => any;
}

It might be useful for some use cases. For example, in NestJS, it would allow a custom error that inherits their HttpException class (or just their ForbiddenException) (if I remember the name correctly haha), which is catched and handled automatically.

[psibean]

Looks good to me. One thing I'd add is that, since you are changing the interface, to allow adding a factory function instead of the CsrfErrorConfig (one or the other). Something like:

Could be useful, it's also a non-breaking (backwards compatible) change so will consider it separately from this one. 👍🏻 It's typically what the error handler middleware should be setup to do in any case.