Skip to content
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

Modularizing the API #40

Open
UltCombo opened this issue Oct 11, 2015 · 0 comments
Open

Modularizing the API #40

UltCombo opened this issue Oct 11, 2015 · 0 comments

Comments

@UltCombo
Copy link
Member

es20xx is great at handling JS workflows, but I don't want to include the whole front-end tooling (e.g. CSS and HTML preprocessors) in the gulpfile.

I believe we should be able to provide a way for users to require() the build and watch tasks in their gulpfiles, so they can incorporate es20xx into their existing workflows and seamlessly update es20xx without manually editing the gulpfile.

This will not change the current slush generator, but rather expose an API that registers the es20xx gulp tasks. I'll probably split the slush-es20xx API into another package, then users can require the API directly.

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant