Open jamesobrooks opened 2 years ago
Hello @jamesobrooks,
Thank you for using our products and for letting us know about this issue. Until the next product update, we'll ask you to make the following change:
package.json
and replace the devDependencies with the following ones:
"devDependencies": {
"gulp": "^4.0.2",
"gulp-autoprefixer": "^7.0.1",
"gulp-clean": "^0.4.0",
"gulp-install": "^1.1.0",
"gulp-sass": "^5.1.0",
"gulp-sourcemaps": "^2.6.5",
"gulp-open": "^3.0.1",
"sass": "^1.49.9"
},
Hope this information helps you. Please let us know if we can help you with anything else.
All the best, Stefan
@groovemen,
Thanks! That worked well, and I think actually fixed another strange issue I was having. I was previously getting errors even running npm i
from GitBash and had to use Windows' built-in command prompt. Now I can run everything from GitBash as usual.
Hello again,
That's great! Good to hear that.
Cheers, Stefan
Version
1.0.9
Reproduction link
https://github.com/creativetimofficial/ct-soft-ui-design-system-pro
Operating System
Windows [Version 10.0.19044.1645]
Device
Dell
Browser & Version
n/a
Steps to reproduce
cd
intosoft-ui-design-system-pro-html-v1.0.9
directorynpm install
npm start
What is expected?
npm start
should successfully start the application.What is actually happening?
The script exits with status code 1. The following is the terminal output.
Error: Cannot find module 'sass' Require stack:
gulp open-app
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the soft-ui-design-system-pro@1.0.9 open-app script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\james\AppData\Roaming\npm-cache_logs\2022-05-11T02_25_19_645Z-debug.log npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! soft-ui-design-system-pro@1.0.9 start:
npm run open-app
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the soft-ui-design-system-pro@1.0.9 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\james\AppData\Roaming\npm-cache_logs\2022-05-11T02_25_19_686Z-debug.log