Ok, peerDependencies downloaded too.

So, if we want to avoid node-sass and sass installed at the same time, we have to remove them :/

Does this mean that mom install sass --dev is sufficient to replace node-sass with sass?

Or, is there an option to specify the sass engine to be used?

Yes, you have to install rollup-plugin-scss and sass (or node-sass).

Like one of:

• npm install rollup-plugin-scss sass --save-dev
• npm install rollup-plugin-scss node-sass --save-dev

Until this is merged, you can try

• npm install @astappiev/rollup-plugin-scss sass --save-dev

rollup-plugin-scss will not use sass automatically until this PR is merged and a new version released. There is workaround like setting sass in configuration (like sass: require('sass'),), but it will anyway install node-sass even if not used.

If you use my patched version @astappiev/rollup-plugin-scss, you can verify that node-sass doesn't exist in node_modules directory.

Done

It is nice that for v3, the dependency is being removed completely. Just a quick question here:

In v2.6.1, the dependency was already moved towards optionalDependencies -- yet the npm release still includes it under dependencies.

Did something go wrong with the deployment, causing the discrepancy?

From the downloaded package.json:

{
  "_resolved": "https://registry.npmjs.org/rollup-plugin-scss/-/rollup-plugin-scss-2.6.1.tgz",
  "dependencies": {
    "node-sass": "4",
    "rollup-pluginutils": "2"
  },
  "optionalDependencies": {
    "node-sass": "4"
  },
}

Seems to be a "feature": npm/npm#3502

1. Thank you for the great work with this plugin. Now that I am running @astappiev/rollup-plugin-scss version, dart-sass compilation is instantaneous. This is the fastest scss development I've ever experienced and a huge improvement from sassc. And, it watches the whole tree (If you look at the snowpack plugin you'll see they're having issues with this part).
2. When can I replace this version with the stock version in my installation? Has v3 been released?