Remove user agent - Refused to set unsafe header "user-agent"

[jjaybrown]

Modern browsers will now reject custom headers being set for user-agent, can the user agent setting on browser/UMD be removed to prevent this error?

[leebenson]

Setting the user agent should actually not be happening in the browser module.

Are you using @timberio/browser, or the node package?

[jjaybrown]

Timber node, but it is a React SPA application and uses the winston log transport.

import { Timber } from '@timberio/node'
import { TimberTransport } from '@timberio/winston'

[leebenson]

Gotcha.

@timberio/node is designed specifically for server-side/Node environments. It uses the Node.js API (such as the built-in streams package), so even if we were to change the User-Agent setting to satisfy the browser, there's no guarantee that other current or future changes would work in the browser.

I'd recommend having separate entry points for the server/browser - you can use the @timberio/js package to instantiate a Browser/Node variant as described here.

That should solve the User-Agent issue for you, but also guarantee that you're using the right version to match the environment.