-
Notifications
You must be signed in to change notification settings - Fork 89
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
task.source doesn't take effect after a yeild task #289
Comments
Hi! Unfortunately, this is the only quirky behavior that Taskr has. I haven't been able to spend time sorting it out yet. Taskr's sub-tasks can get, uh, confused if trying to chain/start too many tasks from within tasks. In this case, you can move export async function build(task) {
await task.source('.tmp/index.html').usemin({
staticDir: c.build,
}).target(c.build);
await task.start('compile');
} But I recommend keeping all tasks unqiue/simple and then running them from the CLI (or npm script) like this: export async function build(task) {
await task.source('.tmp/index.html').usemin({
staticDir: c.build,
}).target(c.build);
} // package.json
{
"scripts": {
"build": "taskr compile build"
}
} Either of those should work for you. Your plugin is fine 😄 |
I write a simple build task and a custom plugin
usemin
as following.I thought the
files
argument of the generator function in theusemin
plugin should be.tmp/index.html
but, I found that I'm wrong, it contains all the files which returned by thehtml
task.so why things become so weird? (maybe I should post this question on stackoverflow. sorry ....
The text was updated successfully, but these errors were encountered: