- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2020 11:20 PM
When I prepare the environment of the new UI framework in orlando, at the step of now-cli develop, it always shows error:
Error: Cannot find module '@servicenow/cli-component-archetype/package.json'
I've installed the package in the project folder and I can find the package.json file in the node_modules:
Any help?
Solved! Go to Solution.
- Labels:
-
Agent Workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2020 11:31 PM
Dear Dirk,
I solved this problem by the following steps:
npm install -g node-gyp
npm install --global --production windows-build-tools
npm cache clean -f
npm install
npm install node-sass (manully, maybe need npm rebuild node-sass if it doesn't work)
Now, it works fine.
Thank your, Dirk!
BR
Daniel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2020 04:35 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2020 04:40 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2020 04:53 AM
Hi
Not sure, if that is an issue.
I have "node" v12.16.2 and "npm" version 6.14.4.
My CLI version is 17.0.2
BTW: Running the
> now-cli develop
TAKES some seconds to respond. Keep cool and wait some seconds (for me around 15 seconds on a Surface Book).
Let me know, if you could proceed with the updated NPM and NODE Versions.
BR
Dirk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2020 05:44 AM
It wait for a long time and no build logs.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2020 04:57 AM
BTW: can you paste the content of the "package.json" file? it must match in version as well - I guess.. For me it mentioned also Version 17.0.2. And you are running your component in 17.0.3
Maybe that mixes up something as well...
BR
Dirk
PS: Did you download your "Hello-World" somewhere, so that I can also try to find out, if that issue happens on my machine as well?
Let me know.
BR
Dirk