Atom 1.63.1 Native Module Compatibility During Environment Migration

Answer

No. Native addons cannot be built against the host Node 18+ runtime and loaded in Atom 1.63.1. Atom 1.63.1 ships Electron 13.1.7, ABI 93. A native module must be compiled against the Electron 13.x headers and ABI, not against the system Node version. Rebuilding is possible with the correct target flags, but success depends on toolchain and glibc compatibility on the host. There is no official, documented way to bypass the archived apm metadata API. A practical workaround is to install a native package from a local path so apm does not need to resolve it from the archived registry.

Confirmed facts

• Atom 1.63.1 is pinned to Electron 13.1.7. Native Node.js addons loaded by Atom must match that Electron ABI.
• apm and the Atom package repository are archived. Remote metadata lookups can fail or be stale.
• node-gyp can target Electron via --target and --dist-url. The Electron headers are fetched from https://atom.io/download/atom-shell for this version.

Likely explanation vs uncertainty

Likely: Rebuilding with electron-rebuild or node-gyp rebuild --target=13.1.7 --arch=x64 --dist-url=https://atom.io/download/atom-shell produces a .node binary that Atom 1.63.1 can load without modifying core source.

Uncertain / requires verification: Host glibc compatibility. Atom core was built against glibc ~2.27. Rebuilding on a host with a newer glibc is generally acceptable for forward compatibility, but a newer toolchain can introduce build warnings and a binary that will not run on older glibc hosts. The exact Node 18+ host toolchain is not a blocker for the build itself, because the target is Electron, not Node. Container isolation is feasible to guarantee a legacy build environment, but it adds IPC and filesystem complexity for language servers.

Steps needed for this case

1. Identify target: Electron 13.1.7, ABI 93, arch matching the Atom install.
2. On the build machine ensure Python 3.x, node-gyp, and a C++ compiler are present.
3. Rebuild the native module against Electron headers:

   npm install --save-dev electron-rebuild
   npx electron-rebuild --target=13.1.7 --dist-url=https://atom.io/download/atom-shell

   Or directly:

   node-gyp rebuild --target=13.1.7 --arch=x64 --dist-url=https://atom.io/download/atom-shell

4. Copy the resulting build artifacts into the Atom package location. For a local package, place the rebuilt binary under node_modules of the package.
5. Force local install with apm to avoid registry lookup:

   apm install --dev --no-optional --no-atom-dependencies

   With a package.json dependency pointing to a local path, apm will use the local copy instead of querying the archived registry.

Verification

• Open Atom 1.63.1 and run apm list --installed to confirm the package is listed locally.
• Load the package and check the Developer Tools console for Error: Module did not self-register or ABI mismatch errors.
• On Linux, check glibc: ldd --version. Host glibc must be >= the one used to build Atom, typically 2.27.

Missing diagnostic detail that changes recommendation: Host OS and architecture, and the specific native module name and its build scripts. Knowing glibc version and whether the module uses prebuilt binaries vs node-gyp determines if a container with node:14-bullseye is required.