@stylexjs/babel-plugin runtimeInjection option behavior change between 0.3 and 0.4

[HorusGoul]

The problem

There are cases in which we might want runtimeInjection: false (like when developing an SSR app), but we still want to use dev: true to provide dev friendly class names.

On the latest version of @stylexjs/babel-plugin, the code changed from

stylex/packages/babel-plugin/src/utils/state-manager.js

Lines 86 to 87 in 4e1be33

	runtimeInjection:
	(options: $FlowFixMe).runtimeInjection ?? !!(options: $FlowFixMe).dev,

to

stylex/packages/babel-plugin/src/utils/state-manager.js

Lines 99 to 106 in a3528b6

	runtimeInjection:
	options.runtimeInjection === true
	? DEFAULT_INJECT_PATH
	: options.runtimeInjection
	? options.runtimeInjection
	: options.dev
	? DEFAULT_INJECT_PATH
	: undefined,

Before, the plugin used ??, which checked for null and undefined; now, it uses ternaries, which check for falseness. This means it will ignore an explicit runtimeInjection: false configuration and fall back to checking for dev.

How to reproduce

Steps to reproduce:

1. Using the babel-plugin, pass dev: true and runtimeInjection: false.
2. Runtime will be injected.

Expected behavior

Plugin shouldn't inject the runtime if runtimeInjection is set to false

Environment (include versions). Did this work in previous versions?
0.4.1 version of the babel plugin.
It did work in 0.3.0.

[nmn]

I already have a PR up to fix this. #298

[nmn]

Fixed in 0.5.0