Missing type definitions for node.js http.incomingMessage
I'm wondering why http.IncomingMessage.aborted is not defined in "@types/node": "^10.12.6". If I run the following code aborted works as expected. That is, if I kill the transaction aborted is true; otherwise it's false.
import * as http from 'http';
let server = http.createServer((req: http.IncomingMessage, res: http.ServerResponse) =>
{
// pretend to do some processing...
setTimeout(() => {
let aborted: boolean = (req as any)['aborted'];
console.log(`response aborted ${aborted}`);
res.end(`the endn`);
}, 2000);
}).listen(80);
Aborted has been available since v0.3.0 seems strange that it isn't defined.
Cheers.
node.js typescript
add a comment |
I'm wondering why http.IncomingMessage.aborted is not defined in "@types/node": "^10.12.6". If I run the following code aborted works as expected. That is, if I kill the transaction aborted is true; otherwise it's false.
import * as http from 'http';
let server = http.createServer((req: http.IncomingMessage, res: http.ServerResponse) =>
{
// pretend to do some processing...
setTimeout(() => {
let aborted: boolean = (req as any)['aborted'];
console.log(`response aborted ${aborted}`);
res.end(`the endn`);
}, 2000);
}).listen(80);
Aborted has been available since v0.3.0 seems strange that it isn't defined.
Cheers.
node.js typescript
add a comment |
I'm wondering why http.IncomingMessage.aborted is not defined in "@types/node": "^10.12.6". If I run the following code aborted works as expected. That is, if I kill the transaction aborted is true; otherwise it's false.
import * as http from 'http';
let server = http.createServer((req: http.IncomingMessage, res: http.ServerResponse) =>
{
// pretend to do some processing...
setTimeout(() => {
let aborted: boolean = (req as any)['aborted'];
console.log(`response aborted ${aborted}`);
res.end(`the endn`);
}, 2000);
}).listen(80);
Aborted has been available since v0.3.0 seems strange that it isn't defined.
Cheers.
node.js typescript
I'm wondering why http.IncomingMessage.aborted is not defined in "@types/node": "^10.12.6". If I run the following code aborted works as expected. That is, if I kill the transaction aborted is true; otherwise it's false.
import * as http from 'http';
let server = http.createServer((req: http.IncomingMessage, res: http.ServerResponse) =>
{
// pretend to do some processing...
setTimeout(() => {
let aborted: boolean = (req as any)['aborted'];
console.log(`response aborted ${aborted}`);
res.end(`the endn`);
}, 2000);
}).listen(80);
Aborted has been available since v0.3.0 seems strange that it isn't defined.
Cheers.
node.js typescript
node.js typescript
asked Nov 13 '18 at 10:15
OllieOllie
254
254
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The aborted
event was added in v0.3.8 - the aborted
field was added in v10.1.0, which is quite recent.
Therefore it's highly likely that the type definitions just haven't been updated yet - I'd recommend submitting a pull request to add it, so that everyone else can benefit :)
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53278665%2fmissing-type-definitions-for-node-js-http-incomingmessage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The aborted
event was added in v0.3.8 - the aborted
field was added in v10.1.0, which is quite recent.
Therefore it's highly likely that the type definitions just haven't been updated yet - I'd recommend submitting a pull request to add it, so that everyone else can benefit :)
add a comment |
The aborted
event was added in v0.3.8 - the aborted
field was added in v10.1.0, which is quite recent.
Therefore it's highly likely that the type definitions just haven't been updated yet - I'd recommend submitting a pull request to add it, so that everyone else can benefit :)
add a comment |
The aborted
event was added in v0.3.8 - the aborted
field was added in v10.1.0, which is quite recent.
Therefore it's highly likely that the type definitions just haven't been updated yet - I'd recommend submitting a pull request to add it, so that everyone else can benefit :)
The aborted
event was added in v0.3.8 - the aborted
field was added in v10.1.0, which is quite recent.
Therefore it's highly likely that the type definitions just haven't been updated yet - I'd recommend submitting a pull request to add it, so that everyone else can benefit :)
answered Nov 13 '18 at 10:22
Joe ClayJoe Clay
15.4k33450
15.4k33450
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53278665%2fmissing-type-definitions-for-node-js-http-incomingmessage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown