-
Notifications
You must be signed in to change notification settings - Fork 31
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.
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
Allow wild cards in Files array. #3
Comments
Hi. By design this plugin operates with strings only, it doesn't perform any filesystem operations. It replaces your blocks with what you provide without any validations or existence checks. But you made an interesting point actually. Could you please describe in more details what exactly are you trying to achieve? How your workflow works? We'll see if that may be an idea for the next version or there is a better way to do what you wanna do. |
Thks for the quick response. Maybe i am just thinking the wrong way about this. Do you have any suggestion? |
If you have many files i can definitely recommend Browserify It also has debug options which enables working sourcemaps :) Try to look at my other repo https://github.com/VFK/tic-tac-toe-online there i use pretty slick workflow with gulp and browserify. As a solution for your current problem you can use any nodejs module which return an array of files. node-glob would do: var glob = require("glob");
gulp.task('build', function () {
glob("client/js/*.js", function (er, files) {
gulp.src('client/index.html')
.pipe(htmlreplace({
js: files
}))
.pipe(gulp.dest('build'));
}) I'm not sure if it's true "gulp way" though. But it works. |
So what did you decide? Has your problem been solved? I do not see a reason to change the plugin since there is a better way. I think this issue can be closed? |
Hi, sorry for taking so long to answer. Thank you for your help ;) |
Hi,
In my development workflow i want to be able to see all my javascript files, and i don't want to list them all.
Is it possible to support wildcards in the files array?
cumps ;)
The text was updated successfully, but these errors were encountered: