autocorrect-node-linux-x64-gnu is a specialized npm package providing the prebuilt native binary for the `autocorrect-node` library, specifically tailored for x86_64 Linux systems utilizing the GNU C Library. The core `autocorrect-node` library functions as a robust linter and formatter, designed to improve copywriting by intelligently correcting spaces, words, and punctuations across various languages, with a particular focus on CJK (Chinese, Japanese, Korean) and English text. Built on NAPI.RS, it leverages Rust-based native modules for high performance. This platform-specific package is typically installed automatically as a transitive dependency when `autocorrect-node` is added to a project on a compatible Linux environment, eliminating the need for local compilation. The current stable version for the `autocorrect-node` ecosystem, including its associated binaries, is 2.14.0, which was last published approximately a year ago. It offers both a command-line interface and a programmatic API for flexible integration into Node.js applications and CI/CD pipelines.
npm install autocorrect-node-linux-x64-gnuVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to use `autocorrect-node` to lint and format a mixed CJK/English text string programmatically.
Instead of installing this binary directly, install the main `autocorrect-node` package (`npm install autocorrect-node`). It includes logic to automatically detect your system and fetch the correct prebuilt binary, or compile it from source if a prebuilt version is not available.
Ensure your Node.js version meets the `autocorrect-node`'s `engines.node` requirement (current `>= 10`). If issues persist after a Node.js upgrade, try clearing your `node_modules` and `npm cache clean --force`, then reinstalling `autocorrect-node` to force recompilation or download of a compatible binary. Consider using a Node.js version manager like `nvm` to easily switch and manage Node.js versions.
Ensure your Linux environment is up-to-date and includes common system libraries. For Docker, use a robust base image (e.g., `node:lts-slim` or `ubuntu`) and install any necessary runtime dependencies. Error messages will usually indicate the missing library (e.g., 'cannot open shared object file: No such file or directory').
Update or downgrade your Node.js version to match the expected ABI, or clear `node_modules` and `npm cache clean --force` then reinstall `autocorrect-node` to trigger a fresh build or download of the correct binary. Using a Node.js version manager is recommended.
First, ensure you are running `npm install autocorrect-node` (not this binary directly). If the error persists, verify your operating system and architecture are supported. Clear `node_modules`, `package-lock.json`, and npm cache, then reinstall. Check npm logs for specific build errors during installation.
Install the missing system library using your distribution's package manager (e.g., `sudo apt-get install libstdc++6` on Debian/Ubuntu, `sudo yum install libstdc++` on RHEL/CentOS). Ensure your environment is up-to-date.
No dependency data recorded yet.