Fomantic-UI: [build] 'npm install fomantic-ui' fails

Bug Report

Steps to reproduce

mkdir foobar
cd foobar
npm install fomantic-ui

Expected result

fomantic-ui installed without error

Actual result

[15:07:55] Starting 'run setup'...
npm ERR! ? Set-up Semantic UI (Use arrow keys)
npm ERR! ❯ Automatic (Use default locations and all components)
npm ERR!   Express (Set components and output folder)
npm ERR!   Custom (Customize all src/dist values) [15:07:55] The following tasks did not complete: install, run setup
npm ERR! [15:07:55] Did you forget to signal async completion?

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/e1ectr0n/.npm/_logs/2021-03-10T23_07_57_254Z-debug.log

2021-03-10T23_07_57_254Z-debug.log

Version

Fomantic UI: 2.8.8-beta.179 (also tried 2.8.7, 2.8.6, …)
Debian Bullseye
npm 7.5.2
node.js 12.21.0

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 11
Comments: 21 (10 by maintainers)

Commits related to this issue

Update getting-started.html.eco fix document with issue #1911 [build] 'npm install fomantic-ui' fails issue #1911: https://github.com/fomantic/Fomantic-UI/issues/1911#issue-828473251 solution: ... — committed to iworkist/Fomantic-UI-Docs by iworkist 3 years ago
fix(build): improved install instructions fix document with issue #1911 [build] 'npm install fomantic-ui' fails issue #1911: https://github.com/fomantic/Fomantic-UI/issues/1911#issue-828473251 ... — committed to fomantic/Fomantic-UI-Docs by iworkist 3 years ago

Most upvoted comments

There is no node_modules folder after running npm install fomantic-ui. I think npm cleans it up if the install fails?
Fomantic builds properly with the following steps:
- npm install --ignore-scripts fomantic-ui
- cd node_modules/fomantic-ui
- npx gulp install
- npx gulp build
It seems like npm has a problem during the interactive install step (i.e. Set-up Semantic UI (Use arrow keys)). When running npm install fomantic-ui, I can see this message printed out (as shown in my original post), but never have the opportunity to select any of the options (e.g.: Automatic (Use default locations and all components)). npm errors out immediately after printing this message.

+19

damontarry on Mar 11, 2021

@ViciousBadger Node 15 is currently not supported and reported already in #1859

lubber-de on Mar 11, 2021

Unfortunately no. I just reopened the terminal in that folder and ran npx gulp build and it produced the following error [15:13:54] Using gulpfile ~/Documents/Websites/FomanticTest/node_modules/fomantic-ui/gulpfile.js [15:13:54] Starting ‘build’… Building Semantic [15:13:54] Starting ‘build-css’… [15:13:54] Starting ‘Building uncompressed CSS’… [15:13:54] Starting ‘Building compressed CSS’… [15:13:55] Created: …/…/…/semantic/dist/components/reset.rtl.min.css [15:13:55] Created: …/…/…/semantic/dist/components/reset.rtl.css [15:13:55] Created: …/…/…/semantic/dist/components/site.rtl.min.css [15:13:55] Created: …/…/…/semantic/dist/components/site.rtl.css Potentially unhandled rejection [2] Error: Error in plugin “gulp-less” Message: error evaluating function each: variable @colors is undefined in file

… line: 141315:13:55] The following tasks did not complete: build, build-css, <series>, <series>, Building uncompressed CSS, Building compressed CSS [15:13:55] Did you forget to signal async completion?

rsbepvb on May 16, 2021