-
Notifications
You must be signed in to change notification settings - Fork 340
delegate-dom
seems disappeared
#164
Comments
This looks to be yet another package affected by the mass unpublishing by @azer today (see left-pad/left-pad#4). The package On top of that, it looks like @azer didn't just unpublish his own packages but all of the packages that he had access to. https://github.com/npm-dom/delegate-dom is a collaborative project (not owned just by @azer) but was unpublished by @azer. To summarize, both @azer and @n-johnson have created a really bad situation for a lot of people. As a temporary solution we could point to https://github.com/npm-dom/delegate-dom in
|
Yikes, that's a bit harsh. I grabbed the packages in order to prevent someone with malicious intentions from grabbing the package and publishing a virus in its place. I'm more than happy to transfer ownership of any module to its correct owner, I've also been in contact with npm who will be taking back most of the packages later today and replacing with a security warning. |
Thanks @n-johnson. Sorry for the harsh words. I was more than a bit upset late last night as this has affected a lot of projects. I now realize you were trying to do the right thing, it's just not clear when looking at your npm profile (at the time it appeared you might have malicious intentions). Thanks for swooping in to make sure things didn't get worse. |
I trying with dom-delegate as replacement, but it requires a little updates in the code as following: delegate.on(el, 'a', 'click', function (e) {
//.....
}) into delegate(el).on('click', 'a', function (e) {
//.....
}) And it works. Hope you guys find a better way to solve it^^. |
fix for #164 - unpublished delegate-dom (thanks @leftstick)
Thanks for pointing this out and showing how you fixed it @leftstick. Your fix was used in #165. |
Error log as following:
The text was updated successfully, but these errors were encountered: