Tony Ross

@Malvoz, looking at the code I think both of these are currently allowed. Do you happen to have a test case showing these failing? Specifically they're listed as `extensionDirectives` in...

Thanks! Looks like its complaining about the value as opposed to the existence of the directive. This appears to be because we don't account for this in `valueDirectives`: https://github.com/webhintio/hint/blob/190284e5ff577b6bc0600b1425e7abb39818ced8/packages/hint-http-cache/src/hint.ts#L144 And...

Hi @fahensha and thanks for offering to submit a PR! Yes, your summary is correct. And accounting for the extension values will probably need to happen either before this check...

@fahensha, this definitely sounds like some of our build/bundle steps aren't running correctly. If you're on a branch with some changes already, can you open a draft PR so we...

@fahensha looks like it's our turn to apologize for the delay over the holidays. Sorry about that. I don't currently know of a live URL with this issue, though we...

Thanks @Simbiat! @fahensha do you think you'll have an opportunity to verify your changes against this site and post a PR?

Thanks for the report @aladdin-add! Looks like webhint is incorrectly only looking for this using a relative path resolution and not a require-based resolution, judging from the code in utils-json/src/final-config.ts:...

Thanks for the report @giorgioskizzo! Are you able to share the URL you were trying to analyze with webhint when this error occurred? That would help us reproduce the issue...

@giorgioskizzo unfortunately it looks like the attachment didn't make it from the mail through GitHub. If this was opened using the `file://` it's possible the browser is blocking the extension...

Thanks for the report @ChrisGitIt! I think in this case the format you're using to specify the character encoding in the content type header is incorrect. Updating your server config...