Using jsbeautifyrc is broken

[Leandros]

Reproduction Rate:
3/3 - 100%

Steps to Reproduce:

• Create empty .jsbeautifyrc: echo "{}" > .jsbeautifyrc
• Run this command: js-beautify -r --config .jsbeautifyrc

Result:

$ js-beautify -r --config .jsbeautifyrc.2
[SyntaxError: Unexpected token i]
Error while loading beautifier configuration file.
Run `js-beautify -h` for help.

Expected Result:
js-beautify should properly execute.

Additional Information:
You can repeat the step 1 with any valid jsbeautifyrc, even the samples in this repository fail.
I'm using version 1.6.2 fresh installed via NPM.

[bitwiseman]

I don't see that syntax error.
That said, the command line you provided is not valid. The one that would work is:

js-beautify.js -r --config .jsbeautifyrc .jsbeautifyrc

Or if you want run it on the code in this repo:

./js/bin/js-beautify.js -r --config .jsbeautifyrc .jsbeautifyrc

I'm not sure where the error you're getting is coming from, but I would still say this is a bug: the beautifier should report that path to the configuration file it fails to load.

[Leandros]

It used to work.

My script ran the beautifier, by feeding the results of find into js-beautify like this:

find ./lib/ -type f -name "*.js" -exec js-beautify -r --config .jsbeautifyrc {} \;

And it worked absolutely perfectly, until I've had to get the new version today. I, unfortunately, can't tell you the old version.

[michaeljonathanblack]

Experiencing the same bug. I am running js-beautifier within Atom successfully, however running it from the command line is no bueno.

$ js-beautify -r --config .jsbeautifyrc src/js/test.js

Is anyone aware of a good indent-fixing alternative? eslint's --fix for indent is also not working correctly. Had trouble with prettifier, too. Indent-fixing all my files is just not happening today.

[Leandros]

You can use an old version of jsbeautifier. This is what I resorted to.

It's still a mystery to me, how someone can break the most simple use case.

[bitwiseman]

@mherodev

Experiencing the same bug. I am running js-beautifier within Atom successfully, however running it from the command line is no bueno.

How is it "no bueno"?

[bitwiseman]

@Leandros - Which older version did you resort to?

[Leandros]

I was still on 1.6.2. Which is weird.
I, however, found out how and why it's broken. I had a malformed .jsbeautifyrc in another directory (a few directories up), which was picked up, even though I pointed to a completely different file.

I have two suggestions:

1. Search from the current directory up for a file matching the specified filename, not the other way around.
2. Improve the error messages. They're completely unusable in the newest version, they were, sort of good, back in 1.5.10. The pointed to the error and pointed out what the error was. Only missing was the actual file where the error occurred in (it's printed as undefined), that would make finding the error a lot easier.

[bitwiseman]

@Leandros - I've added error output.

I don't understand your first suggestion. Could you elaborate?

[bitwiseman]

@Leandros - I'm goint to mark this a closed for now. Please respond when you have a chance.