creativetimofficial / ct-soft-ui-design-system-pro

Soft UI Design System PRO - Premium Bootstrap 5 UI kit
https://www.creative-tim.com/product/soft-ui-design-system-pro
16 stars 2 forks source link

[Bug] Running `npm install` and `npm start` after unzipping #30

Open jamesobrooks opened 2 years ago

jamesobrooks commented 2 years ago

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

  1. Unzip archive
  2. cd into soft-ui-design-system-pro-html-v1.0.9 directory
  3. Run npm install
  4. Run 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.

    
    C:\Repos\soft-ui\soft-ui-design-system-pro-html-v1.0.9>npm start

soft-ui-design-system-pro@1.0.9 start C:\Repos\soft-ui\soft-ui-design-system-pro-html-v1.0.9 npm run open-app

soft-ui-design-system-pro@1.0.9 open-app C:\Repos\soft-ui\soft-ui-design-system-pro-html-v1.0.9 gulp open-app

Error: Cannot find module 'sass' Require stack:

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



---
### Solution

### Additional comments

<!-- generated by creative-tim-issues. DO NOT REMOVE -->
groovemen commented 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:

All the best, Stefan

jamesobrooks commented 2 years ago

@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.

groovemen commented 2 years ago

Hello again,

That's great! Good to hear that.

Cheers, Stefan