typescript and @types/react errors
I'm still learning to use typescript with react. Due to how slow react-scripts-ts was, I was turned off from it. I've tried the new typescript setup with babel 7 (react-webpack-typescript-babel) and its exceedingly fast. However there are some basic errors that I can't resolve.
Even though the project runs, in vscode I get the following errors:
- [ts] Module ...@types/react... has no exported member 'Component'
- [ts] Property 'setState' does not exist on type 'Counter'
- [ts] Module ...@types/react... has no exported member 'SFC'
- [ts] Unknown compiler option 'esModuleInterop'
- and more...
I'm assuming this is a @types/react and typescript issue.
- Is @types/react not being updated?
- How I can get the other properties to show up?
- I also don't understand when to download from
@types vs use the @types found in some packages other than reading
the package description.
javascript reactjs typescript typescript-typings
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
add a comment |
I'm still learning to use typescript with react. Due to how slow react-scripts-ts was, I was turned off from it. I've tried the new typescript setup with babel 7 (react-webpack-typescript-babel) and its exceedingly fast. However there are some basic errors that I can't resolve.
Even though the project runs, in vscode I get the following errors:
- [ts] Module ...@types/react... has no exported member 'Component'
- [ts] Property 'setState' does not exist on type 'Counter'
- [ts] Module ...@types/react... has no exported member 'SFC'
- [ts] Unknown compiler option 'esModuleInterop'
- and more...
I'm assuming this is a @types/react and typescript issue.
- Is @types/react not being updated?
- How I can get the other properties to show up?
- I also don't understand when to download from
@types vs use the @types found in some packages other than reading
the package description.
javascript reactjs typescript typescript-typings
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
Unknown compiler option 'esModuleInterop'it seems you're using an older version of typescript. That's an option from typescript>=2.7
– lleon
Nov 21 '18 at 19:18
1
Wellreact-webpack-typescript-babelis usingv3.1.6so your local typescript might not be the issue. Maybe you have an older version of typescript globally installed?
– lleon
Nov 21 '18 at 19:23
@lleon Wow. I thought I removed all globals but I was wrong.
– SILENT
Nov 21 '18 at 21:02
add a comment |
I'm still learning to use typescript with react. Due to how slow react-scripts-ts was, I was turned off from it. I've tried the new typescript setup with babel 7 (react-webpack-typescript-babel) and its exceedingly fast. However there are some basic errors that I can't resolve.
Even though the project runs, in vscode I get the following errors:
- [ts] Module ...@types/react... has no exported member 'Component'
- [ts] Property 'setState' does not exist on type 'Counter'
- [ts] Module ...@types/react... has no exported member 'SFC'
- [ts] Unknown compiler option 'esModuleInterop'
- and more...
I'm assuming this is a @types/react and typescript issue.
- Is @types/react not being updated?
- How I can get the other properties to show up?
- I also don't understand when to download from
@types vs use the @types found in some packages other than reading
the package description.
javascript reactjs typescript typescript-typings
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
I'm still learning to use typescript with react. Due to how slow react-scripts-ts was, I was turned off from it. I've tried the new typescript setup with babel 7 (react-webpack-typescript-babel) and its exceedingly fast. However there are some basic errors that I can't resolve.
Even though the project runs, in vscode I get the following errors:
- [ts] Module ...@types/react... has no exported member 'Component'
- [ts] Property 'setState' does not exist on type 'Counter'
- [ts] Module ...@types/react... has no exported member 'SFC'
- [ts] Unknown compiler option 'esModuleInterop'
- and more...
I'm assuming this is a @types/react and typescript issue.
- Is @types/react not being updated?
- How I can get the other properties to show up?
- I also don't understand when to download from
@types vs use the @types found in some packages other than reading
the package description.
javascript reactjs typescript typescript-typings
javascript reactjs typescript typescript-typings
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
edited Nov 21 '18 at 19:10
SILENT
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
asked Nov 21 '18 at 18:59
SILENTSILENT
789920
789920
Unknown compiler option 'esModuleInterop'it seems you're using an older version of typescript. That's an option from typescript>=2.7
– lleon
Nov 21 '18 at 19:18
1
Wellreact-webpack-typescript-babelis usingv3.1.6so your local typescript might not be the issue. Maybe you have an older version of typescript globally installed?
– lleon
Nov 21 '18 at 19:23
@lleon Wow. I thought I removed all globals but I was wrong.
– SILENT
Nov 21 '18 at 21:02
add a comment |
Unknown compiler option 'esModuleInterop'it seems you're using an older version of typescript. That's an option from typescript>=2.7
– lleon
Nov 21 '18 at 19:18
1
Wellreact-webpack-typescript-babelis usingv3.1.6so your local typescript might not be the issue. Maybe you have an older version of typescript globally installed?
– lleon
Nov 21 '18 at 19:23
@lleon Wow. I thought I removed all globals but I was wrong.
– SILENT
Nov 21 '18 at 21:02
Unknown compiler option 'esModuleInterop' it seems you're using an older version of typescript. That's an option from typescript >=2.7– lleon
Nov 21 '18 at 19:18
Unknown compiler option 'esModuleInterop' it seems you're using an older version of typescript. That's an option from typescript >=2.7– lleon
Nov 21 '18 at 19:18
1
1
Well
react-webpack-typescript-babel is using v3.1.6 so your local typescript might not be the issue. Maybe you have an older version of typescript globally installed?– lleon
Nov 21 '18 at 19:23
Well
react-webpack-typescript-babel is using v3.1.6 so your local typescript might not be the issue. Maybe you have an older version of typescript globally installed?– lleon
Nov 21 '18 at 19:23
@lleon Wow. I thought I removed all globals but I was wrong.
– SILENT
Nov 21 '18 at 21:02
@lleon Wow. I thought I removed all globals but I was wrong.
– SILENT
Nov 21 '18 at 21:02
add a comment |
1 Answer
1
active
oldest
votes
Based on @lleon input, an old typescript version was the cause of my headache. I removed it npm un -g typescript, added vscode user setting "typescript.tsdk": "node_modules\typescript\lib" and restarted vscode. Works well so far.
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
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%2f53418891%2ftypescript-and-types-react-errors%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
Based on @lleon input, an old typescript version was the cause of my headache. I removed it npm un -g typescript, added vscode user setting "typescript.tsdk": "node_modules\typescript\lib" and restarted vscode. Works well so far.
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
add a comment |
Based on @lleon input, an old typescript version was the cause of my headache. I removed it npm un -g typescript, added vscode user setting "typescript.tsdk": "node_modules\typescript\lib" and restarted vscode. Works well so far.
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
add a comment |
Based on @lleon input, an old typescript version was the cause of my headache. I removed it npm un -g typescript, added vscode user setting "typescript.tsdk": "node_modules\typescript\lib" and restarted vscode. Works well so far.
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
Based on @lleon input, an old typescript version was the cause of my headache. I removed it npm un -g typescript, added vscode user setting "typescript.tsdk": "node_modules\typescript\lib" and restarted vscode. Works well so far.
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
answered Nov 21 '18 at 21:05
SILENTSILENT
789920
789920
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53418891%2ftypescript-and-types-react-errors%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
Unknown compiler option 'esModuleInterop'it seems you're using an older version of typescript. That's an option from typescript>=2.7– lleon
Nov 21 '18 at 19:18
1
Well
react-webpack-typescript-babelis usingv3.1.6so your local typescript might not be the issue. Maybe you have an older version of typescript globally installed?– lleon
Nov 21 '18 at 19:23
@lleon Wow. I thought I removed all globals but I was wrong.
– SILENT
Nov 21 '18 at 21:02