# Node version requirement by Sage 9

**URL:** https://discourse.roots.io/t/node-version-requirement-by-sage-9/18666
**Category:** sage
**Created:** 2020-07-15T12:12:05Z
**Posts:** 5

## Post 1 by @hejamartin — 2020-07-15T12:12:05Z

Hi,

What is the requirement of Sage 9?  
I got some issues with having to new Node, which gives me troubles. Node-sass etc.

So having a to modern use of Node is not the best, which version is Sage made for?

---

## Post 2 by @strarsis — 2020-07-15T15:58:57Z

It is helpful to use a tool like nvm to manage the node version to be used:

> **[nvm-sh/nvm](https://github.com/nvm-sh/nvm)**
>
> Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions - nvm-sh/nvm

---

## Post 3 by @alwaysblank — 2020-07-15T16:26:36Z

The [documentation](https://github.com/roots/sage/tree/9.0.9#requirements) states `>=8.0.0`, so I’d start around there. Usually the LTS version (current 12) is also a good bet.

w/r/t to `node-sass` you can sometimes resolve problems there by switching to `sass` (the reference implementation in Dart). It’s fairly straightforward unless you’ve got some major customization to you build process: Remove `node-sass` from your dependencies and add `sass`–they use compatible APIs. Sometimes you need to change the [`implementation` value in your `sass-loader` definition](https://webpack.js.org/loaders/sass-loader/#implementation) to make sure Webpack knows which one to use. IME Dart SASS has been a lot easier to work with (way fewer problems w/ `npm install`).

---

## Post 4 by @shintaro — 2020-08-25T02:49:46Z

If I raised the version of Node-sass to 4.13.0, I was able to build it with node v12.18.3.

---

## Post 5 by @system — 2020-08-26T12:12:07Z

This topic was automatically closed after 42 days. New replies are no longer allowed.