Semantic-UI-Meteor: Unknown import: themes/default/globals/site.variables.import.less

getting this on trying to use the package:

=> Your application has errors. Waiting for file change.
=> Modified -- restarting.                    
=> Errors prevented startup:                  

   While processing files with flemay:less-autoprefixer (for target web.browser):
   client/lib/theme.import.less:20: Unknown import:
   themes/default/globals/site.variables.import.less

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 17 (3 by maintainers)

Most upvoted comments

same here. deleting .custom.semantic.json makes no difference.

client/semantic-ui/theme.import.less:20: Unknown import: themes/default/globals/site.variables.import.less

Deleting everything but the original custom.semantic.json seems to be a temporary solution, doesn’t help anymore.

This fixed it, but is a bad solution: https://forums.meteor.com/t/whats-up-with-semantic-ui/12331/12 Also this seems to shed light on the problem: https://github.com/meteor/meteor/issues/5598

Real fix Ahhaa, seems that adding site: true to the definitions is mandatory, that’s where the globals folder comes from. Also reset seems to be important for default styling.

KristerV on Jul 10, 2016

@jeveloper as soon as you set default to false in custom.semantic.json and save, meteor removes the client/lib/themes/default/ folder, so the 'default' pathname values in theme.config.import will present a wrong path down the line.

There is also one file path thats hardcoded in theme.import.less:20

/* Default site.variables */
@import "@{themesFolder}/default/globals/site.variables.import.less";

So it might be a good idea to leave default installed.

Most, if not all, themes are just overrides of the default theme. So removing the default theme, might be more problematic and might force every thememaker to include everything.

Why not just put your theme into the /site folder and leave it default? The /themes folder gets regenerated and shouldn’t be edited anyway.

@aesmon did https://github.com/Semantic-Org/Semantic-UI-Meteor/issues/74 work for you? As in …

stop meteor
delete .custom.semantic.json
start meteor

I just did a fresh install of semantic and i also had to stop meteor before it generated the inital files and folders, maybe we should add that step to the docs too.

nooitaf on Feb 23, 2016

I found the solution here worked: #74

micimize on Jan 18, 2016

thanks @KristerV, that fixed it for me as well

kevinkorte on Aug 26, 2016

+1 Exact same issue

breagan1983 on Feb 23, 2016

Does the less package work in this situation?

flemay on Nov 14, 2015