Description
npm install -g cntx-ui@latest (v3.1.13 on registry) produces a broken install. Native Node.js addon binaries are missing, making the CLI unusable when installed from npm. Only npm link from a local source checkout (with npm rebuild) works.
Reproduction
npm install -g cntx-ui@latest
cntx-ui version
Error 1: tree-sitter-sql
Error: Cannot find module '../../build/Release/tree_sitter_SQL_binding'
Require stack:
- .../node_modules/tree-sitter-sql/bindings/node/index.js
Error 2: sharp (if sharp is still a dependency)
Error: Cannot find module '../build/Release/sharp-darwin-x64.node'
Affected native modules
All tree-sitter grammars and sharp rely on prebuilt binaries or node-gyp compilation at install time. When published to npm and installed globally, the binary artifacts are either:
- Not included in the published tarball (
files / .npmignore excludes build/)
install / postinstall scripts that compile native addons are skipped or fail silently during global install
prebuild-install (used by tree-sitter) can't locate compatible prebuilts for the user's platform
Environment
- OS: macOS (darwin-x64)
- Node: v22.17.1
- npm: installed via nvm
- cntx-ui registry version: 3.1.13
- cntx-ui local version: 3.1.15 (works via
npm link + npm rebuild)
Suggested fix
Consider one or more of:
- Bundle prebuilds for supported platforms (darwin-x64, darwin-arm64, linux-x64) using
prebuildify so binaries ship inside the npm tarball
- Add
optionalDependencies for platform-specific packages (similar to how @rollup/rollup-darwin-x64 works)
- Verify
postinstall scripts run during npm install -g by testing in CI before each publish
- Audit
.npmignore / files in package.json to ensure build/Release/ dirs are not excluded from the published package
Impact
Any user running npm install -g cntx-ui gets a completely non-functional CLI. This blocks the v1.0 public release.
Description
npm install -g cntx-ui@latest(v3.1.13 on registry) produces a broken install. Native Node.js addon binaries are missing, making the CLI unusable when installed from npm. Onlynpm linkfrom a local source checkout (withnpm rebuild) works.Reproduction
Error 1:
tree-sitter-sqlError 2:
sharp(if sharp is still a dependency)Affected native modules
All tree-sitter grammars and
sharprely on prebuilt binaries ornode-gypcompilation at install time. When published to npm and installed globally, the binary artifacts are either:files/.npmignoreexcludesbuild/)install/postinstallscripts that compile native addons are skipped or fail silently during global installprebuild-install(used by tree-sitter) can't locate compatible prebuilts for the user's platformEnvironment
npm link+npm rebuild)Suggested fix
Consider one or more of:
prebuildifyso binaries ship inside the npm tarballoptionalDependenciesfor platform-specific packages (similar to how@rollup/rollup-darwin-x64works)postinstallscripts run duringnpm install -gby testing in CI before each publish.npmignore/filesinpackage.jsonto ensurebuild/Release/dirs are not excluded from the published packageImpact
Any user running
npm install -g cntx-uigets a completely non-functional CLI. This blocks the v1.0 public release.