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.

Sign up for GitHub

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

Jump to bottom

Concatenation seems to be using a cache #109

Closed

stones opened this issue Nov 17, 2015 · 1 comment

stones commented Nov 17, 2015

When I pipe my filtered javascript files into concat, it seems to use a cached version because none of my changes are there.

If I don't concatenate them, the individual files are correct.

Any ideas?

edit:
Sorry, that wasn't very instructive. I forgot to mention I have:

deleted my destination files to make sure that the file is a fresh version
I have drastically changed the files ( removing 90% of the content )
I have deleted my npm folder
updated to the current version
Made a new gulp task which pipe all filtered JS into a new folder, and another function to read that folder for all js to concatenate
Output concatenated file to separate folder.

stones closed this as completed

Author

stones commented Nov 17, 2015

SORRY!

It was working as expect.
I had 2 data sets that are very similar being concatenated and I was checking the wrong one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment