Closed ragulka closed 10 years ago
Done.
However, I didn't add the dependency to jQuery in the package.json because currently, I cannot express this dependency in the code. In other words: if I added the dependency, you would still need to load jQuery explicitly wherever you use jquery-simulate-ext since it isn't loaded automatically.
Is this an issue for you anyway? Would Require.js solve this? On the other hand: with Require.js I would introduce a new dependency just to make the other dependency easier to handle. xD So this would make things more complicated for browser usage.
Well, my use case is that I am using your plugin to test my client-side jQuery plugin in node, without launching a browser. I am sinulating the browser/DOM using jsdom. So I am taking care of the jquery dependency myself.
It would be great in the longer run, though, if you could refactor/repackage this plugin so that it runs both in the browser and node, with automatic dependency resolving on node.
Hey, would be great if you could publish this module on npm. npm does allow front-end only packages/modules and a lot of them are already there, including jquery.
It would make it a bit easier to do dev deps management.