Skip to content
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] Upgrading from 2.3 to 2.4 breaks the build #6690

Open
franckboudraa opened this issue Nov 28, 2018 · 3 comments
Open

[Build] Upgrading from 2.3 to 2.4 breaks the build #6690

franckboudraa opened this issue Nov 28, 2018 · 3 comments

Comments

@franckboudraa
Copy link

franckboudraa commented Nov 28, 2018

Steps

  • Install Semantic-UI 2.3.1 to root/src/semantic/
  • Build with gulp build in root/src/semantic/
  • Copy content of gist : https://gist.github.com/franckboudraa/0ab22ff1e29581c04041496aa54774fd
  • Ok, the page is correctly displayed.
  • Drop the dist/ folder in root/src/semantic/
  • Update Semantic-UI to 2.4.2
  • Build with gulp build in root/src/semantic/
  • The page is no longer displayed correctly

Expected Result

capture d ecran 2018-11-28 a 13 03 23

Actual Result

capture d ecran 2018-11-28 a 13 16 10

Version

2.4.2

Testcase

No problem on 2.4.2 fresh install, only when upgrading from 2.3 to 2.4

@franckboudraa franckboudraa changed the title [Build] Upgrading from 2.3 to 2.4 broke build [Build] Upgrading from 2.3 to 2.4 breaks the build Nov 28, 2018
@xeophin
Copy link

xeophin commented Dec 31, 2018

Happened to me as well. Upon checking my theme.config file, I realised that it didn't contain the new placeholder element, and added it between @loader and @rail, like this:

@loader     : 'default';
@placeholder: 'default';
@rail       : 'default';

Then the build process work again.

I guess the theme.config file isn't touched during updates, therefore missing the new component?

@franckboudraa
Copy link
Author

Awesome, thank you @xeophin !

@reallistic
Copy link

reallistic commented Feb 7, 2019

Just happened to me. FWIW, the plumber error config seems to try to alert you of this but it is configured to check line 5 instead of line 9.

You can see this here:

if(error.filename.match(/theme.less/)) {
if(error.line == 5) {
element = regExp.variable.exec(error.message)[1];
if(element) {
console.error('Missing theme.config value for ', element);
}
console.error('Most likely new UI was added in an update. You will need to add missing elements from theme.config.example');
}

The error I received (after manually logging it) is for line 9:

error { [Error: Recursive variable definition for @placeholder in file semantic/src/theme.less line no. 9]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants