Incorrect handling of dotfiles with default basePath about grunt-contrib-compress

[ctalkington]

yes its mainly to do with fact that dots can be part of folder names on some OS and theres no quick solid way to handle multiple dots as filename. auto basePath isn't perfect and was designed to make life easier atleast most the time.

can you run with --verbose and tell me what basePath is being used and atleast a sample config.

[stratoukos]

here is the relevant part of the gruntfile.

Since I'm not specifying basePath it defaults to false and is then converted to '.' in compress.js:117. Then, in line 128, grunt.util._(relative).strRight(basePath) strips the leading ..

I would provide the output of grunt -v, but it exposes much more information about my project than I'm comfortable with. I hope this isn't a problem.

[ctalkington]

@stratoukos thanks, ill see if i can build a test with dotfiles and figure out where its getting the . from in basePath cause with presentation it shouldnt find any common parts.

[ctalkington]

also just to note, if you use newer versions of grunt-contrib-compress, the mode option is automatic by extname.

[ctalkington]

i think I see the issue. it looks like in your case, dirname is returning a . for the presentation.html file. this plus your dotfiles makes . be the basePath.

[ctalkington]

for now, if you want to work around this, you could move everything up a level or pass any string (maybe / since its trimmed anyways). im going to see about improving the basePath in the next week.

[ctalkington]

ok so gruntjs/grunt-lib-contrib@9f93104 should address this. should be pushed by next week.

[stratoukos]

Thanks for looking into this. I'm working around this by passing a random string as the basePath.

[ctalkington]

this should be resolved with newer lib-contrib, atleast as much as we can without breaking other methods. hope it helps!