Closed kgodard closed 10 years ago
The latest version of lineman utilizes lineman-less
, which has its own plugin configuration. Much of your existing config/application.coffee
can be deleted. The parts that are relevant to keep are coffee.app
and js.vendor
. I would try removing the rest and see if that sorts your problem out. Chances are your userland config is overly specific and is conflicting with the config leftover from previous versions of lineman that contained that stuff in core instead of plugin configs.
If you use the latest version of Lineman, and generate a new app structure (lineman new my-app
) you can see just how little is included by default in config/application.coffee
and config/files.coffee
for a comparison :)
Dave, thanks for the pointer in the right direction. It was in fact the lineman-less
plugin config that was causing the issue. This fixed it:
config/application.coffee
concat_sourcemap:
css:
src: [
"<%= files.css.vendor %>"
"<%= files.css.app %>"
"<%= files.less.generated %>"
]
On our project, when generating
app.css
, previous versions of lineman added our compiled LESS css after our vendor css files, like:In the latest version of lineman as of this minute (0.28.3), it's concatenating the CSS files in the opposite order, with our project CSS (app.less.css) first, then the vendor CSS.
here's the top of our
app.css.map
file, in which you can see the order of the included files:This is causing problems because there are a few things that in the vendor CSS that we've overridden in our styles.
I've searched through all of the config files in lineman for a way to specify the order, but I can't figure out where it's being specified.
our config/files.coffee:
lineman/config/plugins/concat_sourcemap.coffee (unaltered):
css
section of lineman/config/files.coffee (unaltered):