VS Code Extension Error Activating extension ServiceNow.now-vscode failed: Cannot find module keytar

[Todd O]

I've been using the ServiceNow VS Code extension for years and love it.  As of yesterday, the extension stopped working and I see this message when I toggle the developer tools with the help menu. 

Activating extension 'ServiceNow.now-vscode' failed: Cannot find module 'keytar'

If I try to activate the Extension (cmd-shift-p Activate Now Extension), I get this error.

I did make a few changes yesterday to my system and they may be related but I'm not finding any solutions for this on the web, communities, etc. Here is my system details and what I've done recently that may be related to my issue.

1. I upgraded my Macmini yesterday MacOS to Sonoma yesterday. I also restarted VS Code as it asked me to update as well. Therefore, my system is fully up to date with latest MacOS, VS Code, the SN Extension and the extension dependencies.
2. I completely removed VS Code from my system and reinstalled. Still getting same error. 
3. I completely uninstalled extensions and reinstalled. Still getting same error.
   1. Version of Extension: ServiceNow® Extension for VS Codev1.6.1
   2. Version of VS Code:Version: 1.83.0 (Universal)

Here is a very interesting detail as well. I have a Macbook Pro computer too and work on that just the same. I did all the exact same upgrades on my Macbook Pro that I did on my Macmini. However, my Macbook Pro does NOT have this problem after the upgrade. That is, the SN VS Code extension works perfectly on my Macbook Pro while it's broken on my Macmini. Any help is greatly appreciated.

Todd

[chrisf · Accepted solution]

I started getting the error after VScode updated to its September release. Once I installed the August 2023 version the extension started working again.

[rohitsengar · Accepted solution]

@Tobias Persson_ I can't give your exact date but we are planning to fix and release a working extension by November month.

[Todd O]

That is great news and great work to you and the team!

[7bitew]

This is great news! Working like a charm. 

I was hoping the included linting rules would be updated to enable support of the latest ES6 features or allow us to configure our own linting rules. It's really difficult to edit application files that are using these features since the plugin doesn't sync back to the server when there are errors. 

[Kundan Thakur]

Hi @7bitew,

We can understand your pain.

The ES6/12 support for extension and other linting issues are in our pipeline and will try to deliver it to our customers asap.

Thankyou.