Invalid or Unexpected Token

[hacdias]

Run the command:

echo "hello" | ./node_modules/.bin/commitlint

Expected Behavior

Get the results.

Current Behavior

PS D:\Code\ipfs\aegir> 
D:\Code\ipfs\aegir\commitlint.config.js:1
(function (exports, require, module, __filename, __dirname) { ��m
                                                              ^

SyntaxError: Invalid or unexpected token
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:152:10)
    at Module._compile (module.js:624:28)
    at requireFromString (D:\Code\ipfs\aegir\node_modules\require-from-string\index.js:28:4)
    at parseJsFile (D:\Code\ipfs\aegir\node_modules\cosmiconfig\dist\loadJs.js:15:15)
    at <anonymous>

Affected packages

• cli
• core
• prompt
• config-angular

[hacdias]

Sorry. Windows line endings...

[escapedcat]

Hey @hacdias could you elaborate your solution to this Windows line issue? Other users facing this issue as well and we're not too familiar with using this in a Windows environment. Thanks.

[hacdias]

@escapedcat as far as I remember, the issue was with what I cloned. If you clone with certain line endings (CRLF), then Node wasn't able to read the files since they ended up with 'CRLF' instead of 'LF'. I'm not sure if that should be a bug anymore or if it is related at all with commitlint or Node.js itself.

Looking at the issue, that seems to have been the problem, but I'm not sure either. It was a long time ago. Sorry for that

Ref.: https://help.github.com/en/articles/dealing-with-line-endings

[sycIsAGod]

Change the file code to UTF-8