Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Koa TypeScript - Type Definition request
See original GitHub issueI am using Koa and TypeScript for server-side development.
Since Koa 2.0.0 is being developed in ES2015, it will be helpful to provide type definitions and reference them in koa’s package.json file for automatic IDE integration and type assistance.
This requirement is also discussed here: https://github.com/borisyankov/DefinitelyTyped/issues/4796
Issue Analytics
- State:
- Created 8 years ago
- Reactions:40
- Comments:16 (9 by maintainers)
Top Results From Across the Web
TypeScript with Koa: Part — 2. Type Definitions ... - Medium
To parse request body, we're going to use the koa-bodyparser package which can handle a number of content types for us. If we...
Read more >Extra robustness in your Koa projects with Typescript
This short blog post will show how you can add more robustness to your controllers by typing your bodies thanks to a simple...
Read more >@types/koa - npm
TypeScript definitions for Koa. Latest version: 2.13.5, last published: 5 months ago. Start using @types/koa in your project by running `npm ...
Read more >Koa + TypeScript: Property 'body' does not exist on type Request
This package contains types introduced by koa-bodyparser (such as request.body) Follow this answer to receive notifications.
Read more >Build a basic API with TypeScript, Koa, TypeORM - Inviqa
Installing @types/node will install the type definition for the latest version. If you're running NodeJS 8 then you'll need to specify your ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
-1 from me personally, koa is a javascript project. If it could live in its own project I could see it being added to the koajs org though.
I think this is a good idea. To clarify, it’s only about a definition file. Not rewriting the whole project. Express has definitions too. It allows awesome IntelliSense in VS Code for example by just doing
tsd install koa. At the moment the definitions are all in the DefinitelyTyped Repo but there are many discussions to move to an approach where frameworks bundle their definitions.