Please heavens warn folks before swapping from old.JSLint to the new version! (and blasting the settings)

[ruffin--]

The update silently wiped out my settings file too. Not great.

I think it's worth putting in an option to use the old JSLint, not that it's difficult to replace the file locally, if you know where it's found. The new ES6 friendly JSLint (which I assume recently came out of beta?) gets much more opinionated than what's up at old.jslint.com -- no this, more draconian about loops, etc. I'm not sure that should be passively updated for plugin users. I realize the options have largely changed too, but you should keep the old ones if users have set them.

Boy, unexpected fun this afternoon.

[rangercyh]

how can I use the old version :(, unhappy now!!!!

[rangercyh]

ok,I know how to use the old version ,now

[liberborn]

@rangercyh I'm facing the same issues. Please describe how to roll JSLint back to previous version?

[liberborn]

OK. just made git clone of this project, reverted it to previous version and replaced content of the package in Sublime. Stable commit: 8c99cc3e1420a9e411961c75ec28fa03164d9f8a.

Very unexpected stuff in very inconvenient time. It's not only about indentation. All of my JS files started producing so many errors. And no information in documentation how to configure JS Lint right.

[zhangdingding]

@liberborn did it right.

[YorkshireKev]

Reverting to previous commit worked for me. Thanks @liberborn

[rangercyh]

yes,I do the same ,it's a pity

[nicholasblexrud]

git clone https://github.com/73rhodes/Sublime-JSLint.git && cd S ublime-JSLint && git reset --hard 8c99cc3e1420a9e411961c75ec28fa03164d9f8a && git clean -f

Then Sublime Text > Preferences > Browse Packages > JSLint remove all files and copy and paste new files

[ruffin--]

A few important tips, I guess, if you want to do this without bothering with gitting... NOTE: I also think, if you haven't set auto_upgrade_ignore, you might end up having your pulled version overwritten later as well. That would stink. ;^)

• See the auto_upgrade_ignore option for the Sublime Text package manager.
• Add JSLint to auto_upgrade_ignore in Preferences > Package Settings > Package Control > Settings – User [1].
• Quit Sublime Text 2
• Blast (delete) your current JSLint package folder.

  • (on Windows, that's likely `C:\Users\YourUserNameHere\AppData\Roaming\Sublime Text 2\Packages`)
    

• Head to your ST backups folder to get the old plugin
  • (on Windows, that's likely C:\Users\YourUserNameHere\AppData\Roaming\Sublime Text 2\Backup)
• Grab the one with the JSLint folder in it that's closest to the date of the change.
• Copy and paste the JSLint folder from your backups folder into your packages folder.

---

[1] Edit: I think I screwed this up initially. As this faux-bug explanation says:

My guess is that you placed it in the wrong settings file. It should be in Preferences > Package Settings > Package Control > Settings – User and NOT Preferences > Settings – User.

[73rhodes]

Hey. Sorry for that. You can use any version of jslint though - it's configurable so you can use the version that ships with the ST package or another version somewhere else on your system. As for user preferences getting hosed, that totally sucks and I'm not sure if it's an ST thing or some crap with this package. Can you provide any other details?

[73rhodes]

refer to https://github.com/douglascrockford/JSLint/commit/f819cf3c65d07086cf217c549c577fa77dc65fc9#commitcomment-14603692