You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The actual main entry point in package.json file is :
"main": "dist/t3.js"
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 :
"main": "dist/t3-native.js"
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:
This would be a breaking change as there are some things jQuery allows you to do (custom selectors, focusin, etc.) that native does not. Some discussion around that point: #22
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 package.json and the hosted files. This will be a breaking change, so we'll hold off until to get some non-breaking changes in first.
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: