-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: unable to install semantic-ui #976
Comments
Same problem here. |
Had the same problem, but I think I know what the problem is: Semantic UI uses an interactive CLI to install (parts of) Semantic UI. By canceling yarn add semantic-ui and navigating to the package folder inside node_modules, using gulp for the install script you get the interactive CLI and from there you can install Semantic UI as you please. |
Confirm very similar problem here, with OSX 10.12.1, Yarn 0.17.9, Node 7.2.0. However, in my case I have So I think there's something else going on as well as @flipvrijn's suggestion. |
A potential clue. Here is the output from
The
I suspect it's something to do with SUI's use of |
Just bumped into this issue. Output I'm getting...
|
I'm not sure if this will be helpful to anyone else; But I'm using react in my project with semantic-ui-react and found that the easiest way for me to avoid this error until the bug is fixed is to just use the semantic-ui-css package and then in my build process add a step to copy the necessary files from node_modules/semantic-ui-css to my output folder. |
^^ Good shout @CaffeinatedCM for people that only need final CSS files. I'm also using Side note, if you're using webpack you can use the style/css-loader and reference SUI CSS directly without copying them to your own source directory I've investigate this a little further. This was failing only on my Docker builds at first, installing locally worked fine. But then I've been able to reproduce this locally by using |
@bobvanderlinden has created an issue on Semantic-UI to track this |
A similar issue seems to be occuring during a npm install on TFS:
It just sits on the finished prompt. It might be that TFS doesn't attach to any spawned processes properly so maybe the issue is different but the result is the same. |
Have any of the developers had a chance to take a look? It's important to establish whether the bug lies in yarn or semantic ui or else this bug will never get looked at. |
If anyone from yarn team has suggestions on what could be causing the issues let me know. |
Can repro in 0.24 on macos with
|
+1, this would be great. |
Digging into that now. |
Looks like semantic-ui has some interactive installation step that Yarn does not print
|
Does anyone have an idea how to detect that a package is trying to open an interactive console in install scripts? |
this issue also happened when I want to install flexjs.
Then I can't enter anything except Ctrl+C |
@bestander I think give user an interactive building process is an expected operation.But I don't know if it's difficult to implement. |
Had trouble with this recently and just to expand on the answer provided by @BrockReece there is a "semantic.json.example" downloaded into "node-modules/semantic-ui" when running npm/yarn. |
I'm just going to ask here. Did anyone find a workaround with Rails 5.1 on webpack? |
Got it, just change the path to Here's my semantic.json in the root:
|
Although I agree with this, I think we can simply call |
Good idea
…On Mon, Oct 30, 2017 at 4:41 AM Burak Yiğit Kaya ***@***.***> wrote:
When a dependency is trying to steal stdin even in a non TTY mode this
seems to me an antipattern.
Although I agree with this, I think we can simply call stdin.end() on the
spawned script to ensure it never stalls on waiting for user input. What do
you all think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#976 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACBdWCrck0jWMyr1v2DDGr0T8ROO0Naeks5sxbXegaJpZM4KVnPW>
.
|
# The below will hang on: semantic-ui: Starting run setup # yarnpkg/yarn#976 (comment) yarn add semantic-ui --dev # Kill the setup # copy node_modules/semantic-ui/semantic.json.example > root/semantic.ui (and set autoInstall to true) cp node_modules/semantic-ui/semantic.json.example semantic.json # now set autoInstall to true and re-run yarn yarn add semantic-ui --dev # I'm not sure, but you may want to add dist/ to .gitignore # This may require others to run gulp build for the semantic ui assets # but may keep commits cleaner in the future (I dunno?) # import css in your component: app/jacascript/packs/hello_react.jsx # See readme for code that goes in here # ALSO INCLUDE THE stylesheet_pack_tag with the same component name # in the view: app/views/site/signup.html.erb # (this wasted a lot of my time) # see Readme for code that goes in here # reloading the app should apply the semantic-ui styling
@philostler I am trying to build a custom theme in react and am using webpack. What will be the best way to go about it? |
This issue is still persisting with trying to install semantic-ui . Output provided by yarn install |
for 2.3.0, this works for me
PS. if you want to do custom theme, you can edit this file. (https://semantic-ui.com/usage/theming.html#using-packaged-themes). i apply default theme here.(copy from node_modules/semantic-ui/src/theme.config.example) finally do |
@respire it's necessary to remove comments in files. |
Ran into this tonight with 1.5.1 (newest), got it to work by adding the files, running npm install and then yarn install. Edit: Also set auto install to true. Yarn install still hangs. |
There is a simple workaround for this:
Then, we should complete the installation by going to |
#5632) **Summary** Fixes #976. This is a bug fix to the problem where lifecycle scripts that try to go interactive hang yarn installs with no indication as to why. This sets stdin to /dev/null and, on unix-like systems, detaches the process from the terminal making it unable to read /dev/tty. Previously with the spinner enabled was impossible to give input to an interactive script on stdin, because a pipe was kept open from the main yarn process to the child process but it was never written to. Interactive scripts could previously use /dev/tty on unix-likes to bypass this, however the fact that scripts are run in parallel means that if two scripts go interactive in this manner that they'll step on each other. This does not change the behavior if the spinner is disabled. Also added a simple integration test with a blocking install script that times out without the patch. **Test plan** Try running `yarn add semantic-ui`. Hangs without the patch, fails with the patch.
I think I can probably, at the very least, detect yarn and then provide at least a better text explanation of how to finish install. |
This reverts commit 64cc17f. Ref: - yarnpkg/yarn#976
Unfortunately, I experience the same issue with |
Actually |
Thank you so much for this!! I just installed beforehand gulp globally as administrator with this command |
What is the current behavior?
Semantic-UI installation hangs up with the following output:
What is the expected behavior?
the package installs fine.
Please mention your node.js, yarn and operating system version.
Ubuntu 16.04.1 LTS
Node v6.7.0
Yarn v0.15.1
P.S. Semantic-UI has a huge installation script. I guess it relies on some undocumented NPM logic. If I can gather more information for you, tell me how, I'd be happy to help.
The text was updated successfully, but these errors were encountered: