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

Have an opinion--or not--about js source transformations #3

Open
anandthakker opened this issue May 13, 2015 · 3 comments
Open

Have an opinion--or not--about js source transformations #3

anandthakker opened this issue May 13, 2015 · 3 comments

Comments

@anandthakker
Copy link
Contributor

Because we have both gulp and browserify here, there's redundancy in our ability to transform (e.g. minify, transpile, inline assets, etc.) our source files: we can use transform streams in gulp, or we can use browserify transforms.

Do we want to decide on a preferred way to do this (aways allowing for exceptions where they make sense)?

@jflasher
Copy link
Contributor

@anandthakker any preferred approach? I don't think I have a strong preference either way.

@anandthakker
Copy link
Contributor Author

@jflasher I think I have a slight preference for using browserify transforms when possible, the reason being that it theoretically could keep all the js processing in one place, and that if someone wanted to drop gulp or replace it with something else it would be easier.

@kamicut
Copy link
Member

kamicut commented May 15, 2015

+1 for keeping the js transforming in independent modules

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

3 participants