Parsing error: Unexpected token interface












0















Migrating an app from react to use typescript. It's proving a little bit painful



I am getting this error in a .tsx file: Parsing error: Unexpected token interface



where I have



export interface IProps {
propOne: any
propTwo: any
}


any idea why it is doing this?



the interface lies just above my component



export interface IProps {
propOne: any
propTwo: any
}

export const mYComponent = (props: IProps) => {
//component stuff
}


what am I doing wrong?



I've just removed eslint from my project and installed this: https://www.npmjs.com/package/tslint-eslint-rules and I'm using this in just the tslint.json file. not sure why it doesn't like the word interface? :/










share|improve this question























  • It's possible that something about that export has a syntax error which only gets picked up at the word interface, what's above that export?

    – dan
    Jan 2 at 13:22
















0















Migrating an app from react to use typescript. It's proving a little bit painful



I am getting this error in a .tsx file: Parsing error: Unexpected token interface



where I have



export interface IProps {
propOne: any
propTwo: any
}


any idea why it is doing this?



the interface lies just above my component



export interface IProps {
propOne: any
propTwo: any
}

export const mYComponent = (props: IProps) => {
//component stuff
}


what am I doing wrong?



I've just removed eslint from my project and installed this: https://www.npmjs.com/package/tslint-eslint-rules and I'm using this in just the tslint.json file. not sure why it doesn't like the word interface? :/










share|improve this question























  • It's possible that something about that export has a syntax error which only gets picked up at the word interface, what's above that export?

    – dan
    Jan 2 at 13:22














0












0








0








Migrating an app from react to use typescript. It's proving a little bit painful



I am getting this error in a .tsx file: Parsing error: Unexpected token interface



where I have



export interface IProps {
propOne: any
propTwo: any
}


any idea why it is doing this?



the interface lies just above my component



export interface IProps {
propOne: any
propTwo: any
}

export const mYComponent = (props: IProps) => {
//component stuff
}


what am I doing wrong?



I've just removed eslint from my project and installed this: https://www.npmjs.com/package/tslint-eslint-rules and I'm using this in just the tslint.json file. not sure why it doesn't like the word interface? :/










share|improve this question














Migrating an app from react to use typescript. It's proving a little bit painful



I am getting this error in a .tsx file: Parsing error: Unexpected token interface



where I have



export interface IProps {
propOne: any
propTwo: any
}


any idea why it is doing this?



the interface lies just above my component



export interface IProps {
propOne: any
propTwo: any
}

export const mYComponent = (props: IProps) => {
//component stuff
}


what am I doing wrong?



I've just removed eslint from my project and installed this: https://www.npmjs.com/package/tslint-eslint-rules and I'm using this in just the tslint.json file. not sure why it doesn't like the word interface? :/







javascript reactjs typescript






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 2 at 13:16









Red BaronRed Baron

1036




1036













  • It's possible that something about that export has a syntax error which only gets picked up at the word interface, what's above that export?

    – dan
    Jan 2 at 13:22



















  • It's possible that something about that export has a syntax error which only gets picked up at the word interface, what's above that export?

    – dan
    Jan 2 at 13:22

















It's possible that something about that export has a syntax error which only gets picked up at the word interface, what's above that export?

– dan
Jan 2 at 13:22





It's possible that something about that export has a syntax error which only gets picked up at the word interface, what's above that export?

– dan
Jan 2 at 13:22












1 Answer
1






active

oldest

votes


















1














I think you just need to remove the export before interface.



Because you can only export one thing per file.






share|improve this answer


























  • oh my gooooosh. why is that breaking it :/. but yeh seems to have fixed it

    – Red Baron
    Jan 2 at 13:23











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007070%2fparsing-error-unexpected-token-interface%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









1














I think you just need to remove the export before interface.



Because you can only export one thing per file.






share|improve this answer


























  • oh my gooooosh. why is that breaking it :/. but yeh seems to have fixed it

    – Red Baron
    Jan 2 at 13:23
















1














I think you just need to remove the export before interface.



Because you can only export one thing per file.






share|improve this answer


























  • oh my gooooosh. why is that breaking it :/. but yeh seems to have fixed it

    – Red Baron
    Jan 2 at 13:23














1












1








1







I think you just need to remove the export before interface.



Because you can only export one thing per file.






share|improve this answer















I think you just need to remove the export before interface.



Because you can only export one thing per file.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 2 at 13:23

























answered Jan 2 at 13:20









user2846469user2846469

484313




484313













  • oh my gooooosh. why is that breaking it :/. but yeh seems to have fixed it

    – Red Baron
    Jan 2 at 13:23



















  • oh my gooooosh. why is that breaking it :/. but yeh seems to have fixed it

    – Red Baron
    Jan 2 at 13:23

















oh my gooooosh. why is that breaking it :/. but yeh seems to have fixed it

– Red Baron
Jan 2 at 13:23





oh my gooooosh. why is that breaking it :/. but yeh seems to have fixed it

– Red Baron
Jan 2 at 13:23




















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007070%2fparsing-error-unexpected-token-interface%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas