-
Notifications
You must be signed in to change notification settings - Fork 145
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
Change entry point in package.json #76
Comments
Good idea, people using browserify probably have access to es5 or babel. Thoughts @nzakas ? |
This would be a breaking change as there are some things jQuery allows you to do (custom selectors, So the real question is if this is important enough to do now and go to 2.0.0, or if we can wait? |
Just an update: for 2.0.0, we are going to switch the default version of T3 to be the native one, both in |
Breaking: Use NativeDOM by default (fixes #76)
The actual
main
entry point inpackage.json
file is :And this version of T3 still depends on jQuery.
Now that there is a native version of the framework (without jQuery dependency), it would be great to have it included as the new entry point in
package.json
file :It would allow us to
require('t3js')
(with Browserify for example) without the need to require also jQuery and pollute the global scope to make it work with T3.Any thoughts about it ?
Thanks !
The text was updated successfully, but these errors were encountered: