0

I'm having problems running gulp, and other npm installed commands from the local node_modules path.

For example I'll have a script sass that calls gulp sass and invoke npm run sass, and it claims the gulp binary isn't found ('gulp' is not recognized as an internal or external command,) -> but it's definitely there, in node_modules/bin.

A global install of gulp does work, but that's not an acceptable solution.

1 Answer 1

1

This was caused by a so-called cursed WSL directory with setCaseSensitiveInfo set to true, coupled with the default PATHEXT which contains all CAPS extensions. So when you try to run gulp it looks for gulp.CMD but the distributed command is gulp.cmd.

Adding lowercase variants to PATHEXT appears to have fixed it without having to frob setCaseSensitiveInfo to false everywhere.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.