-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Request: Break Velocity Into Modules #4
Comments
👍 @julianshapiro consider component.io for modularity. At worst you should have a component.json file, but if you plan to break it out further, component makes for a pretty robust hierarchy. We use it religiously. Happy to run you through it in our next meet up. |
A simple way how i like to work is just to simply concat the files. So you don't get the overhead of the umd tools. Did this for Hammer.js and am still happy with it :-) |
Jorik, First off, Hammer is AWESOME. Second, I actually prefer your suggestion over the others. I will start doing this beginning this weekend. Meanwhile, I'm also going to take Kyle up on his dinner offer to hear more about component :) |
I'm glad to hear that! If you like, you can take a look at the gruntfile I use for Hammer, contains some basic logic that could be useful. Also i find jshint and jscs very useful for consistent code when people are going to contribute. |
Personally, I recommend gulp instead of grunt for velocity ;) |
This will be happening once we drop the jQuery dependency. Thanks for the suggestions, guys! We'll be using @jtangelder's approach to grunt concatenation. |
Hello
Now velocity is a single big file and it is difficult for many devs to work on it. Could you break it to multiple modules (commonJS, AMD)?
Cheers
The text was updated successfully, but these errors were encountered: