SublimeLinter: SublimeLinter: ERROR: env: node: No such file or directory

For me I have ESLint and SassLint installed.

My various dependencies were installed via homebrew but you can find where your dependencies may be installed by using the which command. E.g. which node -> /usr/local/bin/node.

I got ESLint set up a while back but was trying to get sass-lint working and was seeing the following error:

SublimeLinter: WARNING: sass output:
env: node: No such file or directory

For my setup adding "sass": { "env": {"PATH":"/usr/local/bin/"} } to Sublime test > Preference > Package Settings > SublimeLinter > Settings solved the issue.

Full config for context:

// SublimeLinter Settings - User
{
    "linters": {
        "eslint": {
            "env": {"PATH":"/usr/local/bin/"}
        },
        "sass": {
            "env": {"PATH":"/usr/local/bin/"}
        }
    },
    "paths": {
        "linux": [],
        "osx": [
            "/usr/local/bin/",
        ],
        "windows": []
    }
}

Since you’re trying to get 'sass-lint' to run, you may need to name your property "sass-lint": { "env": {"PATH":"/usr/local/bin/"} }. Good luck!

Seeing this now too - not sure what’s going on, I’m only seeing the following:

SublimeLinter: #61 eslint labs-site-header.js ERROR:
====================================================

env: node: No such file or directory

What file is missing?

Apparently the correct syntax for sass-lint in SublimeLinter v4.10.0 is “sass”.

I’ve just had the same problem.

On the initial install of SublimeLinter and specific linters, they all worked fine. Once I shut down and restarted they stopped working. After reading Robpayot comment, I changed sass-lint to sass and this fixed my issue.

For me I had to add the following to the SublimeLinter settings.

"linters": {
   "sass": {
      "env": {"PATH":"/usr/local/bin/"}
    },
    "tidy": {
       "env": {"PATH":"/usr/local/bin/"}
    },
     "jshint": {
       "env": {"PATH":"/usr/local/bin/"}
    },
},

"paths": {
   "linux": [],
     "osx": [
        "/usr/local/bin/"
      ],
     "windows": [
}

Issues like this make Sublime Text and SublimeLinter not really worth the effort; best to use VSCode! Not sure why this was closed.

I’m still experiencing this. How long before a fix?

Since you’re trying to get 'sass-lint' to run, you may need to name your property "sass-lint": { "env": {"PATH":"/usr/local/bin/"} }. Good luck!

Apparently the correct syntax for sass-lint in SublimeLinter v4.10.0 is "sass".

"linters": {
    "sass": {
        "env": {"PATH":"/usr/local/bin/"}
    }
}

Adding that code to my SublimeLinter settings fixed my error.

My SublimeLinter recently broke due to brew deciding, by itself, that it was time to update my Node version when I did a brew install somepackage.

To fix it, run which node in any terminal. I got this path:

/usr/local/opt/node@16/bin/node

So, in Sublime, issue a CMD SHIFT P and select SublimeLinter Settings. It will open a JSON file. Mine was like this:

// SublimeLinter Settings - User
{
  "debug": true,
  "linters": {
    "eslint": {
      "selector": "text.html.vue, source.js - meta.attribute-with-value", 
    }
  }
}

Then you just add a ENV key, taking care to point to the node FOLDER, not the node binary itself, so the end file was like this:

// SublimeLinter Settings - User
{
  "debug": true,
  "linters": {
    "eslint": {
      "selector": "text.html.vue, source.js - meta.attribute-with-value",
      "env": {
        "PATH": "/usr/local/opt/node@16/bin" // my path to node's binary
      }
    }
  }
}

Save the file and issue a CMD SHIFT P and “Reload sublimelinter and its plugins”. Voilá!

Issues like this make Sublime Text and SublimeLinter not really worth the effort; best to use VSCode! Not sure why this was closed.

It was closed because the solution has been found.

---

This problem happens because the plugin assumes that we already installed all the stuffs they needed in certain location, and don’t consider that we might install them somewhere else. In my case, where the error is:

SublimeLinter: #6 eslint index.js ERROR:
========================================

/usr/bin/env: ‘node’: No such file or directory

The plugin assumed to find node in /usr/bin/, and I solved this problem by installing node with my distro package manager. Like this sudo apt install nodejs. Damn clear, solved. Easy.

But hey, when you’re using Debian and node in its repository is old. You’ll want to install the shiny latest version of NodeJS through external tools like NVM. With that, I had to point each plugin manually to find it in SublimeLinter’s settings file, like this:

  "linters": {
    "eslint": {		// linter name
      "env": {
        "PATH": "/home/user/.nvm/versions/node/v16.13.2/bin/"	// my path to node's binary
      }
    }
  }

Voila! And I went back to work.