You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! notus-svelte@1.1.0 build:fontawesome: mkdir -p public/assets/vendor/@fortawesome/fontawesome-free/webfonts && mkdir -p public/assets/vendor/@fortawesome/fontawesome-free/css && cp -a ./node_modules/@fortawesome/fontawesome-free/webfonts public/assets/vendor/@fortawesome/fontawesome-free/ && cp ./node_modules/@fortawesome/fontawesome-free/css/all.min.css public/assets/vendor/@fortawesome/fontawesome-free/css/all.min.css
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the notus-svelte@1.1.0 build:fontawesome 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:
Solution
The command is for linux, not windows
Additional comments
The text was updated successfully, but these errors were encountered:
Version
1.1.0
Reproduction link
https://github.com/creativetimofficial/notus-svelte
Operating System
Windows 10
Device
PC
Browser & Version
N/A
Steps to reproduce
Follow the instructions at https://github.com/creativetimofficial/notus-svelte
until the command:
npm run build:fontawesome
What is expected?
Completed installation.
What is actually happening?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! notus-svelte@1.1.0 build:fontawesome:
mkdir -p public/assets/vendor/@fortawesome/fontawesome-free/webfonts && mkdir -p public/assets/vendor/@fortawesome/fontawesome-free/css && cp -a ./node_modules/@fortawesome/fontawesome-free/webfonts public/assets/vendor/@fortawesome/fontawesome-free/ && cp ./node_modules/@fortawesome/fontawesome-free/css/all.min.css public/assets/vendor/@fortawesome/fontawesome-free/css/all.min.css
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the notus-svelte@1.1.0 build:fontawesome 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:
Solution
The command is for linux, not windows
Additional comments
The text was updated successfully, but these errors were encountered: