Skip to content

Conversation

@3imed-jaberi
Copy link
Member

Checklist

  • I have ensured my pull request is not behind the main or master branch of the original repository.
  • I have rebased all commits where necessary so that reviewing this pull request can be done without having to merge it first.
  • I have written a commit message that passes commitlint linting.
  • I have ensured that my code changes pass linting tests.
  • I have ensured that my code changes pass unit tests.
  • I have described my pull request and the reasons for code changes along with context if necessary.

@3imed-jaberi 3imed-jaberi self-assigned this Oct 12, 2024
@3imed-jaberi 3imed-jaberi changed the title chore: update readme.md file with notice chore: update readme.md file with notice about the module name Oct 12, 2024
@3imed-jaberi 3imed-jaberi force-pushed the chore/add-notice-about-new-name branch from 9b040d9 to 0b6a649 Compare October 12, 2024 23:41
@3imed-jaberi 3imed-jaberi merged commit d94dfa0 into master Oct 12, 2024
6 checks passed
@3imed-jaberi 3imed-jaberi deleted the chore/add-notice-about-new-name branch October 12, 2024 23:43
@mreinstein
Copy link

This isn't a good decision. According to npm stats, koa-send is downloaded 800,000 times weekly. koa-send works fine, and now we're going to intentionally orphan everyone who doesn't update to @koa/send (hint: the people behind most of the software depending on this module). For what? so we can feel good about things being under a @koa namespace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants