LSP: Not working at all after update, no errors and no functionality

Describe the bug Sublime LSP completely stopped working, possibly in relation to both Sublime and SublimeLSP receiving updates during my vacation. LSP either doesn’t show in the status bar at all or, more commonly, shows LSP-[server] installing... infinitely and there is no autocompletion or other indication of LSP working when editing a file. I have added log_debug: true and log_server: ["panel"] as described in the troubleshooting guide, but no errors are shown in the console.

Opening a .ts file with LSP-typescript and LSP-eslint enabled yields the following related output.

LSP: starting ['/usr/local/bin/node', '/Users/vef/Library/Caches/Sublime Text 3/Package Storage/LSP-eslint/14.7.0/language-server/out/eslintServer.js', '--stdio'] in /Users/vef/Documents/projects/notes/ejendomme
LSP: LSP-eslint: Supported execute commands: ['eslint.applySingleFix', 'eslint.applySuggestion', 'eslint.applySameFixes', 'eslint.applyAllFixes', 'eslint.applyDisableLine', 'eslint.applyDisableFile', 'eslint.openRuleDoc']
LSP: LSP-eslint: supported code action kinds: ['quickfix', 'source.fixAll.eslint']

The statusbar shows the following

I have also tried GraphQL files, which similarly show LSP-graphql installing...

To clarify, everything was working perfectly when I left for holiday three weeks ago.

To Reproduce

• Let Sublime autoupdate LSP to version 4070-1.7.0
• Let Sublime update itself to build 4113

Expected behavior LSP should work just as before the update

Environment (please complete the following information):

• OS: macOS 10.15
• Sublime Text version: 4113
• LSP version: 1.7.0
• Language servers used: LSP: enabled configs: LSP-angular, LSP-eslint, LSP-graphql, LSP-typescript

Additional context

• The path for node as seen in the console output is wrong, since I am using NVM. I expected it to source .zshrc when launcing via terminal but that doesn’t seem to happen.
• SublimeLinter seems to suffer from the same issue
• I have been using FixMacPath, which is supposed to source the shell config, but it’s 7 years old and doesn’t seem to work as expected
• I use PackageResourceViewer to extract packages when needed. The problem persists whether or not LSP and the servers are extracted