Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Skip duplicate configurations. #382
This was referenced
Jun 23, 2014
added a commit
this pull request
Jun 27, 2014
This is great. Thanks for the PR.
In the interest of keeping things DRY, is there a better way to manage "multi-page" apps with usemin?
While the error-checking in this version is greatly appreciated, it'd be even better if we didn't have to carefully keep all of our blocks in sync.
Some options might be:
@schmod That's actually exactly what I am doing. I'm using Metalsmith as a static site generator. I have a partial that lists the script block to be included on each page. It gets rebuilt quickly so local development is still speedy, and I'm not trying to ensure multiple blocks are in sync.
I added the code here that ensures that they are the same, just to be sure people didn't accidentally define blocks that would cause a weird and confusing bug when trying to debug it.
I'm not sure I have the same use case but here's the issue I'm facing, very related to this:
Now my just scaffolded app gruntfile:
A few months ago (latest version) I could modify useminPrepare to:
And it would generate index.12345.css and signin.12345.css and correctly replace them in the .html files as needed. This doesn't work anymore and it throws me:
How can I achieve this with the newest version? Thank you.
+1. I'm using generator-jekyllrb with custom designs for different pages but with shared main.css, modernizr.js and main.js files across the site. After updating, I'm finding that it will no longer let me scan multiple html files to find all the custom css/js files:
If I can't get it to scan all the html files and ignore duplicates, is there any way to bypass useminprepare and manually tell it which files to use?
The way I'm doing it at the moment is to create a throwaway
referenced this pull request
Dec 11, 2014
@plrthink @mCarini86 we just got PR #496 in time for the
This fixed my use case, similar to what @richardwestenra described (sharing main.css across multiple html pages), the only downside is that I have to use the force option now...