Installing fomantic-ui with yarn - gulp install fails

[JamesYFC]

Help Wanted

Problem

Installation with yarn is not working when running with the following

yarn add fomantic-ui --ignore-scripts
yarn --cwd node_modules/fomantic-ui run install

the install (autoInstall mode) gulp task seems to fail due to missing semantic.json?

logs:

yarn run v1.16.0
$ gulp install
[11:58:09] Using gulpfile C:\Projects\TESTTelemetry\create-react-app\rsg-telemetry\front\node_modules\fomantic-ui\gulpfile.js
[11:58:09] Starting 'install'...
[11:58:09] Starting 'run setup'...
[11:58:09] Finished 'run setup' after 1 ms
[11:58:09] Starting 'create install files'...
Auto-Installing (Without User Interaction)
------------------------------
[11:58:09] 'create install files' errored after 1.63 ms
[11:58:09] TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
    at validateString (internal/validators.js:125:11)
    at Object.join (path.js:427:7)
    at C:\Projects\TESTTelemetry\create-react-app\rsg-telemetry\front\node_modules\fomantic-ui\tasks\install.js:273:28
    at taskWrapper (C:\Projects\TESTTelemetry\create-react-app\rsg-telemetry\front\node_modules\undertaker\lib\set-task.js:13:15)
    at bound (domain.js:402:14)
    at runBound (domain.js:415:12)
    at asyncRunner (C:\Projects\TESTTelemetry\create-react-app\rsg-telemetry\front\node_modules\async-done\index.js:55:18)
    at process._tickCallback (internal/process/next_tick.js:61:11)
[11:58:09] 'install' errored after 6.38 ms
error Command failed with exit code 1.

more details below...

#386 (comment)
#386 (comment)

[robclancy]

I came to this package instead of semantic hoping at the very least they had installing working. But here we are still... 2020 and a css framework won't install properly because it hacks in its own installation crap.

[wilpar]

i'm on a quest to have a fully functional install on rails 6, without legacy app/assets. A yarn install would 'complete me'.

[kokogakayui]

Same problem here with a simple yarn add fomantic-ui. That would also help me go full webpack on Rails 6...
Any news on that ?

[cimm]

For Rails there is the Fomantic-UI-SASS gem which seems to work (only tried the styling, not tried the JavaScript).

[davidroeca]

The commands initially described in the issue actually work for me, though I'm using yarn workspaces, so it works, but a little differently:

yarn add fomantic-ui --ignore-scripts
yarn --cwd ../../node_modules/fomantic-ui run install

However, now I need to define a .yarnrc file with the following content:

# Wait for https://github.com/fomantic/Fomantic-UI/issues/811 to be solved
--ignore-scripts true

That will lead to some weird issues if another package I'm relying uses these sorts of scripts, but it's what I'm stuck with for now.

[davidroeca]

Hit another snag. When I handle the steps of the post-install script, I have to manually edit the project root since it's not the repository root. Not a great first installation experience, but fine, it only happens once.

However, when someone clones my repo and tries to run yarn install --frozen-lockfile, the postinstall script tries to run again. Reproduced the issue here.

[davidroeca]

Is there any way this script could not be invoked by default but rather be run via a separate CLI? It seems like something that’s only useful when creating a new project, not something that needs to be run every time. So a helper CLI would probably be preferable e.g. a script that could be run via npx fomantic-setup new-project-dir or something to that effect. Maybe an upgrade utility needs to be added as well.

Another option could be to allow an environment variable of some sort to disable this script. I like this option less, since that environment variable will need to be set on every install for my project, but it would probably lead to fewer breaking changes and is probably easier to implement.

[iamareebjamal]

Hi, couldn't contribute here due to no indication about what the possible course of action should be? SUI's last usable version was installable through yarn as it is currently used by us in the project. This happened only with fomantic UI. I don't thus know what's the stance with the current package, etc but if the customization prompt is to be kept, then it should be separated from the core package and depend on it instead so that people can install core package without any prompt who don't want any customization. For example @fomantic-ui/core can be core package and fomantic-ui can depend on it and prompt users. This way, we'll just use @fomantic-ui/core and be done with it.

[davidroeca]

Commenting here again to mention another work-around I've found by using yarn 2 (berry): https://yarnpkg.com/configuration/manifest#dependenciesMeta

// package.json
{
  // ...
  "dependenciesMeta": {
    "fomantic-ui": {
      "built": false
    }
  }
}

So I'd recommend also trying to upgrade to yarn 2 to resolve this particular issue.