Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sass.cmd is not recognized as an internal or external command #79

Open
benehudson opened this issue May 8, 2023 · 5 comments
Open

sass.cmd is not recognized as an internal or external command #79

benehudson opened this issue May 8, 2023 · 5 comments

Comments

@benehudson
Copy link

Installed product versions

  • Visual Studio: VS 2022 (v 17.5.4)
  • This extension: 1.14.11

Description

I'm getting this error when a *.scss file attempts to compile.
"Error '"C:\Temp\WebCompiler1.14.11\node_modules.bin\sass.cmd"' is not recognized as an internal or external command,
operable program or batch file.
REDACTED C:\Users\redacted...\wwwroot\css\template.scss 0

I have attempted to un-install/re-install twice.

Steps to recreate

  1. Save change to template.scss or right-click and re-compile file.

Current behavior

I get the error message in Description above.

Expected behavior

The file should compile and generate template.css and template.min.css

@benehudson
Copy link
Author

I also did npm install -g sass I'm still getting the same error

@failwyn
Copy link
Owner

failwyn commented May 15, 2023

Can you the following:

  1. Uninstall the Extension,
  2. Delete the Directory C:\Temp\WebCompiler1.14.11\
  3. Install the Extension

Let me know if that works.

@benehudson
Copy link
Author

@failwyn thanks for your reply. I actually got this sorted last week. I thought I posted the fix here. When the install completed there was a NODE_MODULES.cmd (the file name was something like that...it disappeared after it ran) file in the C:\Temp\WebCompiler1.14.11\ I ran that *.cmd and it put the necessary dependencies in the .bin folder. That resolved my issue.

@failwyn
Copy link
Owner

failwyn commented May 15, 2023

Glad to hear it; it seems like there is a permissions issue that causes this to happen, do you run Visual Studio as Administrator?

@benehudson
Copy link
Author

I'm a local admin on the machine where Visual Studio ran, but I did/do not right-click VS and choose run as admin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants