Fomantic and yarn - install issues
See original GitHub issueBug Report
Steps to reproduce
- having an existing package.json with fomantic ui as dep
- lauch
yarn install
- Error while building fomantic ui
Expected result
The installation have no problems
Actual result
error while building fomantic ui
Screenshot (when possible)
Version
fomantic : 2.7.1 yarn : 1.13.0
is fomantic not “compatible” with yarn ?
ps : I’m trying yarn because it’s recommended to build Symfony assets.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:21 (11 by maintainers)
Top Results From Across the Web
Getting Started | Fomantic-UI Docs
If you have any problems or questions please open a issue on the GitHub repository . Installation. You can install Fomantic-UI via NPM...
Read more >Use Semantic UI with Lerna and yarn workspaces
The Semantic UI (and Fomantic UI) installer (famously?) doesn't support yarn because of its interactive postinstall script. Even with " ...
Read more >fomantic-ui-css - npm
Install · Repository · Homepage · Weekly Downloads · Version · License · Unpacked Size · Total Files.
Read more >braintree-web | Yarn - Package Manager
This is the repo to submit issues if you have any problems or questions about a Braintree JavaScript integration. For a ready-made payment...
Read more >How to watch and stream A Love Yarn - 2021 on Roku
2021TVGRomantic comedyromancedramacomedy. The owner of a quaint New Zealand yarn shop gets her world flipped upside down after learning her top supplier of ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mathieutu I just did some more research into this and figured out a way around the issue.
You can install the package and ignore the install script via the following command
This will of course not create your
semantic.json
or install directory so you must run the following command to run the install scriptIMO, running with “–ignore-scripts” is not a solution but, at best, a workaround. Furthermore, if running this in a yarn workspace or by lerna there will be further issues.
Is there any reason this can’t be fixed properly?