cpu-features
cpu-features copied to clipboard
mscdex
A simple node.js binding to Google's cpu_features library for obtaining information about installed CPU(s)
While buildcheck itself seems to support Visual Studio 2022 in version 0.0.4, cpu-features (0.0.4) depends on previous buildcheck "0.0.3". see https://github.com/mscdex/buildcheck/issues/2
``` .../node_modules/cpu-features install: gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3" .../node_modules/cpu-features install: gyp http GET https://nodejs.org/download/release/v18.17.1/node-v18.17.1-headers.tar.gz .../node_modules/cpu-features install: gyp http 200 https://nodejs.org/download/release/v18.17.1/node-v18.17.1-headers.tar.gz .../node_modules/cpu-features install: gyp http...
On macOS, test on the current version of Python to verify there are no distutils issues. * nodejs/nan#986 [Standard GitHub-hosted runners for public repositories](https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories) --> `ubuntu-24.04-arm`, `macos-13`, and `windows-2025`. ```diff...
Tested on x64, loong64 and riscv64. Example output on loong64 ```js { arch: 'loong64', flags: { LAM: true, UAL: true, FPU: true, LSX: true, LASX: true, CRC32: true, LVZ: true,...
## Description The following run target may lead to very complicated errors https://github.com/mscdex/cpu-features/blob/2faca5705cddb7ac388ad2d5e2242b7a7d427f3c/package.json#L16C38-L16C53 When running `pnpm install` on our repository, it try to build the package, and in my case...
LizardByte/setup-python-action is deprecated and has moved to LizardByte/actions.
