Skip to content
This repository has been archived by the owner on Jul 11, 2019. It is now read-only.

delegate-dom seems disappeared #164

Closed
leftstick opened this issue Mar 23, 2016 · 5 comments
Closed

delegate-dom seems disappeared #164

leftstick opened this issue Mar 23, 2016 · 5 comments

Comments

@leftstick
Copy link

Error log as following:

snip20160323_4

@ungoldman
Copy link
Member

This looks to be yet another package affected by the mass unpublishing by @azer today (see left-pad/left-pad#4).

The package delegate-dom was unpublished by @azer and then reregistered by @n-johnson. @n-johnson has for some reason registered hundreds of packages unpublished by @azer then republished them as v2.0.0 with no data (see https://www.npmjs.com/~nj48), making all of them (at least for now) unusable and unrecoverable.

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 package.json.

If you happen to have a project that @azer or @n-johnson are collaborators on, I would suggest removing them. (edit: sorry, that was uncalled for. don't get angry about the internet late at night)

@n-johnson
Copy link

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.

@ungoldman
Copy link
Member

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.

@leftstick
Copy link
Author

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^^.

ungoldman added a commit that referenced this issue Mar 24, 2016
fix for #164 - unpublished delegate-dom (thanks @leftstick)
@ungoldman
Copy link
Member

Thanks for pointing this out and showing how you fixed it @leftstick. Your fix was used in #165.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants