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

Not using the latest css as source #254

Open
Coysh opened this issue Feb 7, 2019 · 0 comments
Open

Not using the latest css as source #254

Coysh opened this issue Feb 7, 2019 · 0 comments

Comments

@Coysh
Copy link

Coysh commented Feb 7, 2019

Description

The manifest.json file being merged with, is containing the correct hash of the compiled SCSS.
Manifest.json is updated (according to filemtime) but not with the correct rev.
Is it possible to fancylog the md5 rev is generating?

	const rev = require('gulp-rev');
	gulp.src([pkg.paths.dist.css + pkg.vars.cssName], {base: 'public/'})
		.pipe(rev())
		.pipe(gulp.dest('./public/'))
		.pipe(rev.manifest('templates/manifest.json',{merge:true}))
		.pipe(gulp.dest('./'));
	$.fancyLog(' -> Processed ['+pkg.paths.dist.css + pkg.vars.cssName+']');```


#### Steps to reproduce
Run `gulp static-assets-version`
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