-
Notifications
You must be signed in to change notification settings - Fork 29
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
Use UMD for module definitions #6
Comments
@lfryc Sorry, but I don't have any experience with UMD, so, pull-request will be great. |
That's right, I would like to.. I face few other problems - the implementation is partially right, but browser implement DOM interface slighly different, thus there will need to be more fixes than initially expected. |
What if I "compile" a single client-side file to use in browser? It will be a part of library. Also, please let me know about fixes you need to work correctly in browser. May be fill an issue? |
Hey Oleg, thanks for your interest, we will release RichWidgets 0.1 with a fork and later in the process I will I also found some issues you already fixed (e.g. whitespace trimming). Ad UMD) An advantage of UMD syntax is that you don't need to care about where a You just need to use universal module definitions specified by UMD project But I haven't use UMD initially in my fork, I just used plain RequireJS - I Ad TESTING) Otherwise testing of dom-compare for browser support will be hard-nut. It Since tests are apparently written in Jasmine, Karma could actually handle On Mon, Oct 7, 2013 at 5:30 PM, Oleg Elifantiev [email protected]:
|
I would like to use dom-compare together with RequireJS (AMD) module loader.
Since dom-compare currently uses Node module definitions (CommonJS-like),
I suggest to use UMD as an universal module loader pattern,
particularly, we could leverage this adapter:
https://github.com/umdjs/umd/blob/master/commonjsAdapter.js
I have already re-factored dom-compare to use just AMD (https://github.com/lfryc/dom-compare/commits/requirejs), but I can open new pull request with refactoring to UMD.
The text was updated successfully, but these errors were encountered: