v2.2.0: regression: open .ls-lint.yaml: no such file or directory

[John Owen Nixon]

After upgrading to ls-lint@2.2.0, ls-lint reports:

open .ls-lint.yaml: no such file or directory

If I rename .ls-lint.yml to .ls-lint.yaml (with an A), it works as before.

But all your documentation says to use .ls-lint.yml.

[Lucas Löffel]

Hey @johnowennixon,

thanks for the report!

can you please share your directory tree and your command? I will take a look rn

[Lucas Löffel]

On my side

bazel run //cmd/ls_lint:ls-lint -- --config ${PWD}/.ls-lint.yml --workdir ${PWD}

works as well

bazel run //cmd/ls_lint:ls-lint -- --config ${PWD}/.ls-lint.yaml --workdir ${PWD}

[John Owen Nixon]

I am simply executing ls-lint in an npm script

Also reproduced by running in a terminal ./node_modules/.bin/ls-lint
And also by running in a terminal npx ls-lint

I am not using --config at all.

All dependencies are updated to latest versions (by deleting package-lock.json and node_modules and re-installing).

If I revert to ls-lint@2.1.0, the problem goes away.

I am using Node v20.8.0
The system is the latest version of Fedora Linux (but I doubt that is relevant).

I think the problem is here: https://github.com/loeffel-io/ls-lint/blob/89059e6b873ee37148ed3be05e27f7c5fe3feb50/cmd/ls_lint/main.go#L47C1-L47C1 and was introduced in this commit 5206390

[Lucas Löffel]

You are absolutely right! Thank you very much for the report
The fix should be online in less then 24 hours

[Lucas Löffel]

v2.2.1 fixes this issue