We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At the moment, if I have a process which adds a cache busting hash at the end of the URL, this plugin no longer works and I get an error such as...
Error: ENOENT: no such file or directory, open 'C:\Users\projectpath\build\css\style.css?cbh=5da92178ce374635e14b17a2e0038469'
I've had to move my "gulp-hash-src" task to after this one, which is fine, but it would be better if it worked either way.
In short, perhaps when loading .js and .css files locally, you could ignore the query string ("?" onwards).
Cheers, Rik
The text was updated successfully, but these errors were encountered:
04ff6e9
Hi Rik, thanks for your report.
With the latest commit, querystrings are now ignored when resolving file paths. That should fix the issue.
I'll make a new release tomorrow.
Sorry, something went wrong.
Great, thanks!
@riklewis v1.4.0 is released.
No branches or pull requests
At the moment, if I have a process which adds a cache busting hash at the end of the URL, this plugin no longer works and I get an error such as...
I've had to move my "gulp-hash-src" task to after this one, which is fine, but it would be better if it worked either way.
In short, perhaps when loading .js and .css files locally, you could ignore the query string ("?" onwards).
Cheers, Rik
The text was updated successfully, but these errors were encountered: