fix(core): enable threading on Linux

[simonklee]

I stumbled over this, but don't see any reason why threading should be disabled on Linux.

Probably wait on #623 to be merged (mostly about testing)

[pkg-pr-new]

@opentui/core

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/core@363ff44

@opentui/react

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/react@363ff44

@opentui/solid

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/solid@363ff44

@opentui/core-darwin-arm64

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/core-darwin-arm64@363ff44

@opentui/core-darwin-x64

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/core-darwin-x64@363ff44

@opentui/core-linux-arm64

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/core-linux-arm64@363ff44

@opentui/core-linux-x64

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/core-linux-x64@363ff44

@opentui/core-win32-arm64

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/core-win32-arm64@363ff44

@opentui/core-win32-x64

npm i https://pkg.pr.new/anomalyco/opentui/@opentui/core-win32-x64@363ff44

commit: 363ff44

[simonklee]

(fail) TestRecorder > should capture timestamps in increasing order [37.45ms]

Seems like a concurrency issue. WIll look into.

[simonklee]

(fail) TestRecorder > should capture timestamps in increasing order [37.45ms]

Seems like a concurrency issue. WIll look into.

Nvm, think its a timing issue.