-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Wrong directory in manifest #200
Comments
What is the structure of I think you need to (1) include |
I have the same issue, even with This is my task: gulp.task('sass', function () {
return gulp.src('scss/*.{sass,scss}', {cwd: './src', base: './src'})
.pipe(sass({
includePaths: [
'./bower_components'
],
precision: 2,
sourceMap: true,
sourceMapEmbed: true,
outputStyle: 'compact'
}).on('error', sass.logError))
.pipe(rev())
.pipe(gulp.dest('./public/css'))
.pipe(rev.manifest({
base: './',
merge: true
}))
.pipe(gulp.dest('./'));
}); This is the {
"scss/bootstrap.css": "scss/bootstrap-55a07f3bb1.css"
} Changing the {
"/vagrant/public/scss/bootstrap.css": "/vagrant/public/scss/bootstrap-55a07f3bb1.css"
} Is there any option to follow the destination path ( I don't want to install other plugins it in order to fix this behaviour. |
Also having a similar issue where we have multiple stand alone js files for different areas, for instance;
And they're all just getting written in the manifest to {
"/dashboards/something/some-feature.js": "/dashboards/something/some-feature-89s8ad7f0ss7d.js"
} instead of what I get now (missing off dashboards from the path); {
"something/some-feature.js": "some-feature-89s8ad7f0ss7d.js"
} If anyone has any work arounds for this atm that'd be really useful |
@Dayjo same problem here, did you find a solution? |
After like 4 hours of searching I finally find fix, how to fix it Before
results in
now
outputs
|
Tell me about it, your solution worked for me also. |
Thank you very much, worked for me |
Please consider this task:
In summary:
Source root folder is
source/
Build root folder is
build/
SCSS gets compiled from
source/scss
intobuild/css
The result is a rev-manifest file in
build/
containing:This is wrong. I would expect it to be:
After all, the manifest is written one level higher, so it should understand that it needs to add the missing part of the path. As a result, gulp-rev-replace doesn't replace the reference to style.css in the html.
Why not save the manifest in the
build/css
folder? Well, somehow that also doesn't work well with gulp-rev-replace. But that's really beside the point. The point is that gulp-rev is generating a manifest that won't work.The text was updated successfully, but these errors were encountered: