Skip to content

--stdin causing a TypeError to be thrown with Node v6 #504

@jrmull

Description

@jrmull

I first noticed this after my linting stopped working in SublimeText using SublimeLinter after installing Node v6. It seems to be related to this change nodejs/node#5348

The error can be seen in the Sublime console (with SublimeLinter in debug mode) or at the shell by:

$ cat test.js | standard.cmd --stdin --verbose
standard: Unexpected linter output:

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.extname (path.js:887:5)
    at processText (C:\Users\user\AppData\Roaming\npm\node_modules\standard\node_modules\eslint\lib\cli-engine.js:144:30)
    at CLIEngine.executeOnText (C:\Users\user\AppData\Roaming\npm\node_modules\standard\node_modules\eslint\lib\cli-engine.js:671:26)
    at Linter.lintText (C:\Users\user\AppData\Roaming\npm\node_modules\standard\node_modules\standard-engine\index.js:66:59)
    at C:\Users\user\AppData\Roaming\npm\node_modules\standard\node_modules\standard-engine\bin\cmd.js:112:16
    at process._tickCallback (internal/process/next_tick.js:103:7)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions