-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[build] gulp build command not working #5391
Comments
would also like to see this answered as i am having the same issue. ⌛️ |
i tried to resolve this by downloading the semantic zip from the website. |
@simoncarbajal i fixed this by completely removing semantic and reinstalling it. not sure where the cause lies. 🤷♂️ |
Fix is to change e.g. |
@tarkwyn Can you make a pull request to fix this? |
I can confirm that @tarkwynl 's change worked for me. I can provide additional details if needed. |
The camelCase issue didn't cause any problems, however I was unable to successfully The error (with "gulp-uglify": "^3.0.0"):
|
@neokio I also received the perserveComments error, but I had to upgrade my version of node to the latest, to get pass that. I will not very experienced with gulp/node so take my inputs with a grain of salt. |
Interesting! Good advice in general, so I updated node from 7.7.1 to the latest (8.1.3), and reinstalled npm ( The above error still appears, unless I remove both |
The error persists in 2.2.11 ... unable to successfully |
@neokio could be unrelated, but when I said I updated to the latest for Node Js I actually went for LTS, not current. https://nodejs.org/en/ so I went on version 6.11.1 |
I think I found the problem. This issue ... terinjokes/gulp-uglify#265 ... and the latest gulp-uglify release notes reveal that release v3.0.0 of gulp-uglify REMOVED the custom option |
Yep, can confirm the issue. Commenting out L148 & L162 (temporarily) solves it. Tried with older version of Node / npm & latest version too. |
After all, what will be done in the semantic ui ? To remove the option or comment and wait for uglify downgrade ? |
I'll fix the dependencies so that we dont use this version of uglify. Sorry about this guys. |
I'm a little late to the party, but I figure another confirmation can't hurt. Commenting out L148 & L162 worked for me as well. Thanks! |
Commenting out L148 & L162. It worked for me too. |
1 similar comment
Commenting out L148 & L162. It worked for me too. |
Commenting out only worked , can't find out if issue is in gulp-uglify or semantic ui. |
Will get fix in over weekend. Thanks for patience. |
Commenting worked for me, too. Glad I wasn't the only one with this problem, since I'm new to semantic ui and gulp--and I'm on a time crunch! Thanks guys! |
Hi, I found that Uglify plugin changed its options and now preserveComments is obsolete: https://github.com/gruntjs/grunt-contrib-uglify#deprecated-options-from-2x
So, just replacing in these 2 lines in semantic/tasks/config/tasks.js:
with:
worked for me. |
@sergiomar73 Thanks this fixed it |
@sergiomar73 Thanks man, I can confirm this fixes it. |
@sergiomar73 I confirm it too. |
@sergiomar73 It worked. Thanks! |
A weekend late but pushing this now. |
What's the timeline for releasing 2.2.12, @jlukic? |
It's kind of too bad that we have to wait until v2.2.12 is released to see this bug fixed :/ |
@cluxter dont worry, I'm releasing this later tonight. Continuing to jam on issues. Manual fix above should work in interim. |
Hmm, still getting this error with v2.2.12:
|
Hi @jlukic , I tried build a test of semantic and the same problem occured. The file tasks.js |
Patch incoming |
And out |
Hi, @jlukic Thanks a lot. |
Sorry about mistakes with the first fix. |
v2.2.13 works on my side. Thanks a lot @jlukic ! |
Hi, I've been having the exact same issue with 2.2.13. |
Yes, can confirm that default version of nodejs 4.2.6 for ubuntu 16.04 won't work. Needed to upgrade to 6.x.x. Thanks. |
Confirmed that it's a problem related to nodejs version. Fixed with:
then use node.js as usual. |
Plumber found unhandled error: Any idea on this? |
gulp build
can't complete the 'build-assets' phase due to the following error:And is NOT fixed by commenting the following lines:
Steps to reproduce it:
The text was updated successfully, but these errors were encountered: