Semantic-ui: tasks.js expects error.filename

[startswithaj]

https://github.com/Semantic-Org/Semantic-UI/blob/master/tasks/config/tasks.js#L92

This expects that the error will have a filename property. Sometimes other errors can be thrown and caught by this.

When it tries to access error.filename.match it throws.

Cannot call method 'match' of undefined suppressing the real error.

It should be

if(error.filename && error.filename.match(/theme.less/)) {

N.B

Because semantic doesn't version its dependencies you can end up with gulp-autoprefixer 3.0.1 which requires node 12 and will make the semantic build process fail with:

/gulp-less/node_modules/accord/node_modules/when/lib/decorators/unhandledRejection.js:80
        throw e;
              ^
TypeError: Cannot call method 'match' of undefined

which is actually covering up the error:

[Error: no writecb in Transform class]

If you need to fix this force install gulp-autoprefixer to 2.3.1

[alxkolm]

Same problem.

Fast workaround:

rm -rf node_modules/gulp-autoprefixer
npm install [email protected]

[jlukic]

When in doubt remove all the things.

What version of autoprefixer is causing the above errors?

[startswithaj]

@jlukic gulp-autoprefixer 3.0.0 and 3.0.1 both have node 12 dependency. (running 3.0.1 on node 10 is what causes the problem). ~ This is speculation but If your not running npm version 2, I dont think npm version 1 inforces the node version dependency and allows 3.0.1 to install.

I just forced it to 2.3.1 which was the previous version my local npm was resolving prior to 3.0.1.

Someone asked I think how I forced 2.3.1; I just added gulp-autoprefixer 2.3.1 to my projects package.json which is a hackaround but because semantic will take any version its happy with this.

[jlukic]

I see. Thanks for all the additional information.

I'll try to check to see if there's anything I can do against issues when running autoprefixer 3.0.

[maxiaoxiong]

@alxkolm you are right!
thanks!

[TechnicalBro]

Just started using Semantic-UI in my pipeline today,and came across this issue. Installing [email protected] fixed it. Any chance of a global fix, or version update?

[r0bdiabl0]

Just hit with this bug myself, took a few days to find this issue but it fixed it. Please update, thanks!

[brandondrew]

Are we still required to use an ancient version of gulp-autoprefixer? Is there any other fix for this?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

[Dan1ve]

We run into this issue, too :-( A fix would be greatly appreciated, as a downgrade of autoprefixer to some ancient version is not an option for us

[stale[bot]]

There has been no activity in this thread for 90 days. While we care about every issue and we’d love to see this fixed, the core team’s time is limited so we have to focus our attention on the issues that are most pressing. Therefore, we will likely not be able to get to this one.

However, PRs for this issue will of course be accepted and welcome!

If there is no more activity in the next 90 days, this issue will be closed automatically for housekeeping. To prevent this, simply leave a reply here. Thanks!

[CatalanCabbage]

This error still seems to be present, I encountered this in my GitLab-CI routine; any ideas on how to proceed?
I tried the workaround by @alxkolm, it didn't work. 😞
My complete error
For reference: submitted new issue on Fomantic-UI and a question on SO

Any pointers or help would be greatly appreciated!

[iamareebjamal]

Semantic UI is dead, please use fomantic UI

[CatalanCabbage]

Yup, I use Fomantic-UI; commented here just in case, since this bug has been carried over from Semantic to Fomantic.
Anyway, to anybody with this issue, for reference: a PR has been submitted with the fix, will be released in Fomantic 2.8.x :)