The implementation option must be passed to the Sass task

[EgidioCaprino]

nvm use 8.10
npm install spectacle-docs
./node_modules/.bin/spectacle swagger.yml

produces

Running "sass:foundation_scss" (sass) task
Fatal error: The implementation option must be passed to the Sass task.

swagger.yml reports no error on editor.swagger.io.

[NordicGamer]

Hello! Exact same problem. Have you found any solution?

[pablomarambio]

Same here 😢
Travis log of the error has more info.
Do you have a fix?

[smishmash]

I have the same problem. This is recent, probably due to a bug in a dependency. I have an older docker image, and an older install on my mac, that works as expected. Attempting to install the software at a new location produces this error.

Update: grunt-sass (https://github.com/sindresorhus/grunt-sass) had 3.0 released 2 hours before this issue was reported. That's the most likely culprit, especially in light of the error message.

[jurgob]

I have the same problem

[slide13]

smishmash is right. I changed grunt-sass to 2.1.0 in dependency and it worked

[offero]

It's the only dependency that has a "*" for a version number. This is why you don't do that.

[TheIDCo-ScottLeckie]

+1
Changing the dependency to "2.1.0" in packages.json and "npm link" allowed me to work around.
Pull request logged

[auscaster]

Hi all, thanks for the PR it was just merged in.

I'll look at updating spectacle to grunt-saas 3.0 today to see if we can fix outstanding issue #114

[lorem--ipsum]

Just faced the same problem today and solved it by adding the implementation to the sass options in my grunt file:

const sass = require('node-sass');

require('load-grunt-tasks')(grunt);

grunt.initConfig({
	sass: {
		options: {
			implementation: sass,
			sourceMap: true
		},
		dist: {
			files: {
				'main.css': 'main.scss'
			}
		}
	}
});

[relair]

@lorem--ipsum This solution works, in my case I needed to add 'node-sass' to my package.json and install it for it to work, but its nice to have it working with latest version.

[auscaster]

This has already been fixed on the latest package.

…

On Thu, 5 Jul 2018 at 11:03, Marcin ***@***.***> wrote: @lorem--ipsum <https://github.com/lorem--ipsum> This solution works, in my case I needed to add 'node-sass' to my package.json and install it for it to work, but its nice to have it working with latest version. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#156 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGKDGyQc7QwZu633ReA7-dPbNAqTf6sks5uDdZGgaJpZM4U5Qt3> .

[medmin]

@auscaster No. I have to add the "implementation: sass," to fix this problem.

It's 2018.8.21 today.

[codeoriginator]

Yes, I face the same issue with the latest.

[arthurlacoste]

I have the same issue

[tradingbills]

Todays date: Sat Mar 23 20:03:07 PDT 2019
Got handed an old Gruntfile.js and had to use the implementation-fix above from lorem--ipsum and also added the
npm i -D node-sass grunt-sass
and it finally worked