Noemi

Hi @brendonrapp! Thank you for reaching out to us. Consider [`plugin-window-events`](https://github.com/appsignal/appsignal-javascript/tree/develop/packages/plugin-window-events) for reporting uncaught errors as well! I'm not sure if this covers what Honeybadger refers to as "error breadcrumbs"...

## To do - [ ] Add optional history/pushState functionality to `plugin-window-events` (see gist above)

Thanks @pantajoe! We may take another look at this issue soon. In the meantime, [note that we do support Winston](https://docs.appsignal.com/logging/platforms/integrations/nodejs.html#usage-with-winston).

Could be fixed by implementing #527 -- by centralising logging, it would be possible for customers to set a lower log level and ignore this warning.

@tombruijn Done and done. :+1: https://github.com/appsignal/appsignal-javascript/pull/546#issuecomment-1028125522

I have tested that this works with the latest Yarn version (in that it removes the error reported by the customer during the AppSignal build, allowing the build to succeed...

@tombruijn I think you're right, I'll add a changeset of some sort, yes. The thing is, I don't want us to proclaim in the docs again that we support Yarn...

@tombruijn Yeah, the tests are correct to be failing -- now the message is not emitted at all. I'll see what I can do to fix it.

@tombruijn It's been fixed now -- but I've also changed a lot of other stuff in the process. I couldn't understand what the right place to emit these warnings in...

@WesleyYue Did you try setting `NODE_OPTIONS="--require ./tracing.js` as an environment variable? I have not tried it, but that, or a small wrapper script that calls `node` with the right arguments,...