
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2021 01:14 PM
I've went through the steps of installing the ServiceNow CLI, but get this error when I try to scaffold a new UI component.
Command: snc ui-component project --name now-experience-dashboard --description "My First NXF component built at CreatorCon"
Error: Cannot find module 'keytar'
Require stack:
- ~/.snc/.extensions/ui-component/node_modules/@servicenow/cli-glide/connection/auth/credential-manager/keytar-synthesizer.js
I'm running macOs Catalina
I'm running nodeJs version 12.19.0.
I see a version discrepancy with the SNC CLI. The lab says the current version should be 19.0.0, however the command "snc version" shows that I have version 1.1.0. I just downloaded and installed today, so I'm pretty sure I have the latest version.
Thanks for any help!
Ryan
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 06:23 AM
I found an answer in an older community post.
Can simply install the keytar package to resolve.
npm i keytar
But now I have a new error. It seems this lab is more of an exercise in using Now Community. 😄
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2021 03:03 AM
Thank you for sharing the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-28-2021 03:14 AM
Reposting this from my reply in https://community.servicenow.com/community?id=community_question&sys_id=4deca8de1beb4454fff162c4bd4bcbe0:
To anyone experiencing this in 2021 onwards with ServiceNow CLI (the new one), already using node 12 and still running into this error...
I fixed it by going into the ui-component extension folder, then installing keytar@5.0.0 (as required) manually:
$ cd ~/.snc/.extensions/
$ npm install keytar@5.0.0
$ smr snc ui-component --help
Usage: <cmd> [args]
For help, run: <cmd> --help
...
It works after!