Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[fix] npm i @koa/send #149

Open
2 tasks done
vanodevium opened this issue Aug 24, 2023 · 9 comments
Open
2 tasks done

[fix] npm i @koa/send #149

vanodevium opened this issue Aug 24, 2023 · 9 comments
Labels

Comments

@vanodevium
Copy link

When I enter:

npm i @koa/send

I see:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@koa%2fsend - Not found
npm ERR! 404 
npm ERR! 404  '@koa/send@*' is not in this registry.
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Checklist

  • I have searched through GitHub issues for similar issues.
  • I have completely read through the README and documentation.
@vanodevium vanodevium added the bug label Aug 24, 2023
@mreinstein
Copy link

The package is published on npm as koa-send. When @3imed-jaberi commited the typescript re-write, the package name was switched from koa-send to @koa/send but the publish never happened. (this commit 61f8be3)

Unclear why the package was renamed, but for now you'll need to npm i koa-send instead, or install from github commit.

@vanodevium
Copy link
Author

Thanx!

@masterflitzer
Copy link

masterflitzer commented Aug 29, 2023

either the readme should be changed to document koa-send or the package should be published under the currently documented package name @koa/send, currently this is very confusing

@mreinstein
Copy link

I agree, and the solution I'd like to see is the npm module getting published but koajs and express are both mausoleums and effectively dead/dying so I'm not super hopeful these will happen any time soon.

@mreinstein
Copy link

Still waiting on https://github.com/koajs/koa-range to get published too.

@masterflitzer
Copy link

I agree, and the solution I'd like to see is the npm module getting published but koajs and express are both mausoleums and effectively dead/dying so I'm not super hopeful these will happen any time soon.

dying? what is used as alternative then? i just migrated 2 small projects to koa cause i thought it might be leaner than express

@vanodevium
Copy link
Author

Please investiage ranked list

I still use koajs, nest.js uses koajs. It's important.

But, as alternative, you can use fastify at any time.

@masterflitzer
Copy link

thx for the tip

@mreinstein
Copy link

i just migrated 2 small projects to koa cause i thought it might be leaner than express

it's definitely leaner than express, and both projects are still quite usable for now.

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

No branches or pull requests

3 participants