gulp-remember is a gulp plugin that remembers files that have passed through it.
gulp-remember adds all the files it has ever seen back into the stream.
gulp-remember pairs nicely with gulp-cached when you want to only rebuild the files that changed, but still need to operate on all files in the set.
var remember = ;
This example shows a scenario in which you want to wrap all script files in some type of module system, then concatenate into one
app.js file for consumption.
As long as your other plugins can keep up, this example showcases the Holy Grail of Build Tools™ - the ability to build once,
git checkout different-branch (a branch with drastically different files), and have the output be exactly what you would expect.
var gulp =header =footer =concat =cache =remember = ;var scriptsGlob = 'src/**/*.js';gulp;gulp;
Returns a stream ready to remember files.
The name of a specific cache you want to use. You may want to
remember('images') in another.
You can choose not to pass any name if you only care about caching one set of files in your whole build.
Drops a file from a remember cache.
The name of the remember cache on which you want to operate. You do not need to pass this if you want to operate on the default remember cache.
Note: If the name does not refer to a cache that exists, a warning is logged. Thanks to @jcppman for this.
The path of the file you wish to drop from the remember cache. The path is used under the covers as the unique identifier for the file within one remember cache.
Important note! The path you pass to
forget must be the path of the processed file. You may encounter instances where your source file is
some/path/script.coffee while the processed file is
some/path/script.js. Because anything could happen before you
remember a file, it is up to you to know how you need to
forget it with the correct path.
If you want to
forget files using their name history, you might want to use gulp-remember-history.
Another note: If the path does not match a file object that exists in the given cache, a warning is logged. Thanks to @jcppman for this.
Drops all files from a remember cache.
The name of the remember cache you want to wipe. You do not need to pass this if you want to operate on the default remember cache.
Note: If the name does not refer to a cache that exists, a warning is logged.
Get a raw remember cache. This can be useful for checking state of the cache, like whether or not a file has been seen before.
Note: Remembering or forgetting files by interacting directly with this returned object is not recommended.
The name of the remember cache you want to retrieve. You do not need to pass this if you want to retrieve the default remember cache.
See the API note above for the
path argument when
forget can only drop files by their processed path name, not their source path name. In common cases, these two things are equivalent.
Thanks to @brian-mann for bringing this up.
Be aware that this plugin does not make specific attempts to keep your files in any order. For example, if you add a new file governed by a glob you are watching, this file will enter the stream last, even if this file would preceed others alphabetically.
If your build process depends on file ordering, please make use of the gulp-order plugin after
Thanks to @brian-mann for bringing this up.
Copyright (c) 2014 Aaron Haurwitz
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.