Skip to content

Errors every on ST3 launch after Better Javascript #10

Open

Description

@norlin

After Better Javascript install now I have two errors on every ST3 launch. Even after plugin was uninstalled.

bjsplugin_19582be1

Activity

  1. lengstrom commented on Aug 2, 2014

    @lengstrom

    I had the same problem. To fix it, as said in Issue #5, you can do the following:

    I had the same issue. After you remove the Better JavaScript package from sublime, go to
    Sublime Text --> Preferences --> Settings-user ---> look for "ignored_packages" and you will see sublime ignored Javascript. Just delete "Javascript" within the "ignored_packages" then you should be fine.

  2. 9point6 commented on Sep 4, 2014

    @9point6

    I have a similar issue where it happens when Better JavaScript is still installed and I get errors relating to the absence of the regular JavaScript package.

    I believe I am correct in understanding that the regular package should be disabled if you've still got Better JavaScript installed - so is there another solution to this issue?

  3. nrutman commented on Sep 13, 2014

    @nrutman

    I have uninstalled Better JavaScript and completed the step above to remove Javascript from the "ignored_packages" array, and I'm still getting the error. Where does Better JavaScript put the reference to the tmLanguage file? I need to tell Sublime to stop looking for it.

  4. nrutman commented on Sep 13, 2014

    @nrutman

    Turns out the issue was that I had a JS file open whenever Sublime would open...resetting the syntax highlighting to something else, and then back to Javascript fixed the problem.

  5. bitflower commented on Oct 9, 2014

    @bitflower

    I'm still having this issue after uninstall (and on install which is why I want to remove it).

    I did:

    It seems there has been written a symlink or something to the better javascript syntax folders. Is this possible?

    I get the exact error message from above.

  6. kanitw commented on Jul 9, 2015

    @kanitw

    +1 This bug is so terrible!

  7. animanathome commented on Jul 18, 2015

    @animanathome

    +1 on this bug being terrible!

  8. krongk commented on Jul 23, 2015

    @krongk

    I have the same error.

  9. alexsolus commented on Feb 5, 2016

    @alexsolus

    I had the same bugs. I then went to uninstall and it removed all my javascript syntax highlighting (by flagging the "ignore" in my user settings).

  10. zeshanshani commented on Feb 26, 2016

    @zeshanshani

    Worst plugin I've ever come across. Followed uninstall instructions but no luck, still getting same error messages. This plugin should be deprecated and removed if there is no one to fix these bugs. If not, there should be a clear warning that says "You are going to ruin your sublime so be aware before installing this plugin"

  11. zeshanshani commented on Mar 16, 2016

    @zeshanshani

    For anyone else who's still getting error messages after following the uninstallation instructions: Do close all your Sublime windows one by one after following the instructions. I'm on a mac and normally open multiple projects on separate Sublime windows. I even closed all JavaScript files from all projects, but it didn't resolve the error. So I took a deep breath and closed all my Sublime windows (again, one at a time). It eventually resolved the issue. Yay!

  12. foria commented on Apr 16, 2016

    @foria

    +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions