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

Built Asset References Not Replaced For Child Directory Files #193

Open
grayghostvisuals opened this issue Jun 8, 2017 · 1 comment
Open

Comments

@grayghostvisuals
Copy link
Contributor

grayghostvisuals commented Jun 8, 2017

@zont Currently using a setup where compiled site files are placed within the root of dist after usemin is executed and client files go within their own designated directory aptly titled "client." See screenshot below…

screenshot 2017-06-08 00 25 43

Problem is after running the build command, the assets are not replaced for the "client" directory and still possess the build comment line without the replaced references to the newly built assets.

Essentially Root Files Go From This…

<!-- build:css {{site.css}}style.min.css -->
{{#contains 'landing, contact, casestudy, categories' this.basename}}
<link rel="stylesheet" href="{{../site.css}}site.css">
{{/contains}}
<!-- endbuild -->

to this

<link rel=stylesheet href=/css/style.min-d5399c4a.css>

And the files within my "client" directory go from this…

<!-- build:css {{site.css}}style.min.css -->
{{#contains 'landing, contact, casestudy, categories' this.basename}}
<link rel="stylesheet" href="{{../site.css}}site.css">
{{/contains}}
<!-- endbuild -->

to this…

<!-- build:css /css/style.min.css -->

<link rel="stylesheet" href="/css/site.css">
<!-- endbuild -->

The resulting error from the shell is…

site/client/css/site.css not found!

Here is a link to my Gulp File and the template containing my build comments. Appreciate any and all help on this issue.

Gulp File
Default Template Containing Build Comments

@grayghostvisuals
Copy link
Contributor Author

@zont File are now being properly minified, but require a separate task. See issue noted above from my repo's issue tracker.

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

1 participant