Member Avatar for SimonIoa

Hello i am getting these error

node sass could not find a binding for your current environment windows 64-bit with unsupported runtime (59)
when i am typing ionic serve on my command prompt
does anyone knows how can i fix it?

  • 2 Contributors
  • 1 Reply
  • 414 Views
  • 4 Hours Discussion Span
  • Latest Post Latest Post by hericles

Dani AI

Generated

Short explanation — the runtime-number message means the node-sass native binary that your project has installed does not match the Node.js runtime you’re actually running. That happens after a Node upgrade or when a node-sass release doesn’t publish a prebuilt binary for that ABI; rebuilding or reinstalling so a matching binary is downloaded/compiled normally fixes it. (npmjs.com)

Check what you’re running and what the project has. Useful commands are:

node -v
npm ls node-sass

The numeric ABI in the error (the “59” you saw) maps to a specific Node major (it’s the Node ABI for the older Node 9 series), so a mismatch between Node and the node-sass version is the likely cause. If the versions don’t line up you’ll need either a node-sass build that supports your Node, or to run the Node version that your project expects. (npm.io)

Practical next steps (build-order, paraphrasing ): force a rebuild of node-sass bindings for your current Node; if that doesn’t help, remove node_modules and any lockfile and reinstall so node-sass can fetch/compile the correct binary. If compilation is required, make sure the native toolchain is present on Windows (MS build tools + Python/node-gyp prerequisites). If you prefer not to fight native builds, either pick a node-sass release that ships a matching binary for your Node, or switch Node versions with nvm/n. (stackoverflow.com)

Longer-term: node-sass (LibSass) is deprecated — move to the Dart Sass implementation (the npm package named sass) to avoid native binding problems entirely. Installing the pure-JS sass package replaces most workflows that previously depended on node-sass. (npmjs.com)

Checklist: confirm node -v, confirm project node-sass version, attempt rebuild (per ), delete/reinstall node_modules, ensure build toolchain if compile is needed, or upgrade/migrate to sass.

Member Avatar for hericles

Trying running
npm rebuild node-sass

It should help rebuild the correct binding for your setup.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.