4 ms·

> I don't think there's anything malicious going on The dev who copied the code forked someone’s repo, went out of his way to remove attribution and git histor

> I don't think there's anything malicious going on The dev who copied the code forked someone’s repo, went out of his way to remove attribution and git history, sent PRs to replace the original package in other libraries with his own version, and when called out on it got defensive instead of apologizing. I think malicious is a fair way to describe his behavior.

cobby 5y ago
> sent PRs to replace the original package in other libraries Would you mind sharing a link to such PR?
iskin 5y ago
This is Nano Colors author. Even before this Twitter thread we had talk with Colorette author and I added mention to the docs, his name to LICENSE and promised him to not replace Colorette by Nano Colors. The Colorette mention was there 5 days ago.
- noptd 5y ago
  >promised him to not replace Colorette by Nano Colors. And was that before or after you opened several PRs to replace Colorette with Nano Colors?
  - iskin 5y ago
    In my PRs I replace chalk to nanocolors
riffraff 5y ago
I wasn't talking about the specific case, but about the general attitude of the JS ecosystem to replace a library very frequently.