Skip to content

CSS order inverted when comboed #50

soljin opened this Issue Aug 20, 2013 · 3 comments

2 participants

soljin commented Aug 20, 2013

Shaker is generating this url, which is in the exact wrong order:


Most notably is the order of normalize, foundation, base and ads. They are added in the controller of my ShakerHTMLFrame child, thusly:


Here is my shaker config:

Here is my spec config:

The order of CSS is pretty important.

soljin commented Aug 20, 2013

I'm using mojito-shaker 4.0.25 fom npm and mojito 0.7.2

soljin commented Aug 20, 2013

On further inspection it appears that any time a mojit adds assets, those assets are then added to the combo url in the order the mojits were executed and then in alphabetical order.

Defining the assets in the application seems to result in even worse problems. Like duplication and files not being found.

Is there something simple I've messed up in my config?



As you mentioned, the order of the css in the combo url is first the app css followed by the css of each mojit in the order of execution. And within each mojit the order of the css is alphabetical. This is intentional. I've noticed that you are also manually adding assets using ac.assets. You shouldn't have to do this since Shaker automatically adds assets. If you are concerned about the order, then you should name your assets accordingly so that they appear in alphabetical order. Alternatively you can place your assets in a directory called 'void', which tells Shaker to ignore these assets. You can then manually add them using ac.assets and they will appear in the order in which they were added regardless of name. Please let me know if either of these solutions is appropriate for your application.

@aljimenez aljimenez closed this Oct 21, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.