Mixing
Conflicting ESLint config using TypeScript and Prettier in a Nuxt project
I'm trying to set-up ESLint and Prettier for my TypeScript Nuxt.js project. Unfortunately the combination of some ESLint configs produces strange errors.
The example file below validates fine using just prettier from the command line. However using ESLint I get the following error:
2:10 error Parsing error: Unexpected token
1 | export default class User {
> 2 | public name: string;
| ^
3 | }
Strangely if I remove the plugin:vue/recommended extend from my ESLint config, the example file validates just fine. To me it looks like there is a conflict or override that messes with TypeScript files, but I can't figure out exactly what the issue is and how to fix it.
Example file User.ts:
export default class User {
public name: string;
}
ESLint config:
module.exports = {
root: true,
env: {
browser: true,
node: true
},
parserOptions: {
parser: 'babel-eslint',
ecmaFeatures: {
legacyDecorators: true
}
},
extends: [
'typescript',
'plugin:vue/recommended',
'plugin:prettier/recommended',
'prettier/vue'
],
plugins: [
'prettier',
'vue'
],
rules: {
'prettier/prettier': 'error'
}
}
typescript vue.js eslint nuxt.js prettier
asked Jan 2 at 1:59
iMoritziMoritz
171214
add a comment |
I'm trying to set-up ESLint and Prettier for my TypeScript Nuxt.js project. Unfortunately the combination of some ESLint configs produces strange errors.
The example file below validates fine using just prettier from the command line. However using ESLint I get the following error:
2:10 error Parsing error: Unexpected token
1 | export default class User {
> 2 | public name: string;
| ^
3 | }
Strangely if I remove the plugin:vue/recommended extend from my ESLint config, the example file validates just fine. To me it looks like there is a conflict or override that messes with TypeScript files, but I can't figure out exactly what the issue is and how to fix it.
Example file User.ts:
export default class User {
public name: string;
}
ESLint config:
module.exports = {
root: true,
env: {
browser: true,
node: true
},
parserOptions: {
parser: 'babel-eslint',
ecmaFeatures: {
legacyDecorators: true
}
},
extends: [
'typescript',
'plugin:vue/recommended',
'plugin:prettier/recommended',
'prettier/vue'
],
plugins: [
'prettier',
'vue'
],
rules: {
'prettier/prettier': 'error'
}
}
typescript vue.js eslint nuxt.js prettier
asked Jan 2 at 1:59
iMoritziMoritz
171214
Are you using nuxt 2.4.0?
– Al-un
Mar 9 at 19:42
For what it is worth, I am also trying NuxtTS+ESLint. Here is my eslintrc. I am not posting an answer as I haven't tried with more components and stuff
– Al-un
Mar 10 at 18:50
add a comment |
I'm trying to set-up ESLint and Prettier for my TypeScript Nuxt.js project. Unfortunately the combination of some ESLint configs produces strange errors.
The example file below validates fine using just prettier from the command line. However using ESLint I get the following error:
2:10 error Parsing error: Unexpected token
1 | export default class User {
> 2 | public name: string;
| ^
3 | }
Strangely if I remove the plugin:vue/recommended extend from my ESLint config, the example file validates just fine. To me it looks like there is a conflict or override that messes with TypeScript files, but I can't figure out exactly what the issue is and how to fix it.
Example file User.ts:
export default class User {
public name: string;
}
ESLint config:
module.exports = {
root: true,
env: {
browser: true,
node: true
},
parserOptions: {
parser: 'babel-eslint',
ecmaFeatures: {
legacyDecorators: true
}
},
extends: [
'typescript',
'plugin:vue/recommended',
'plugin:prettier/recommended',
'prettier/vue'
],
plugins: [
'prettier',
'vue'
],
rules: {
'prettier/prettier': 'error'
}
}
typescript vue.js eslint nuxt.js prettier
asked Jan 2 at 1:59
iMoritziMoritz
171214
I'm trying to set-up ESLint and Prettier for my TypeScript Nuxt.js project. Unfortunately the combination of some ESLint configs produces strange errors.
The example file below validates fine using just prettier from the command line. However using ESLint I get the following error:
2:10 error Parsing error: Unexpected token
1 | export default class User {
> 2 | public name: string;
| ^
3 | }
Strangely if I remove the plugin:vue/recommended extend from my ESLint config, the example file validates just fine. To me it looks like there is a conflict or override that messes with TypeScript files, but I can't figure out exactly what the issue is and how to fix it.
Example file User.ts:
export default class User {
public name: string;
}
ESLint config:
module.exports = {
root: true,
env: {
browser: true,
node: true
},
parserOptions: {
parser: 'babel-eslint',
ecmaFeatures: {
legacyDecorators: true
}
},
extends: [
'typescript',
'plugin:vue/recommended',
'plugin:prettier/recommended',
'prettier/vue'
],
plugins: [
'prettier',
'vue'
],
rules: {
'prettier/prettier': 'error'
}
}
typescript vue.js eslint nuxt.js prettier
typescript vue.js eslint nuxt.js prettier
asked Jan 2 at 1:59
iMoritziMoritz
171214
asked Jan 2 at 1:59
iMoritziMoritz
171214
asked Jan 2 at 1:59
iMoritziMoritz
171214
asked Jan 2 at 1:59
iMoritziMoritz
171214
asked Jan 2 at 1:59
iMoritziMoritz
171214
171214
Are you using nuxt 2.4.0?
– Al-un
Mar 9 at 19:42
For what it is worth, I am also trying NuxtTS+ESLint. Here is my eslintrc. I am not posting an answer as I haven't tried with more components and stuff
– Al-un
Mar 10 at 18:50
add a comment |
Are you using nuxt 2.4.0?
– Al-un
Mar 9 at 19:42
For what it is worth, I am also trying NuxtTS+ESLint. Here is my eslintrc. I am not posting an answer as I haven't tried with more components and stuff
– Al-un
Mar 10 at 18:50
Are you using nuxt 2.4.0?
– Al-un
Mar 9 at 19:42
Are you using nuxt 2.4.0?
– Al-un
Mar 9 at 19:42
For what it is worth, I am also trying NuxtTS+ESLint. Here is my eslintrc. I am not posting an answer as I haven't tried with more components and stuff
– Al-un
Mar 10 at 18:50
For what it is worth, I am also trying NuxtTS+ESLint. Here is my eslintrc. I am not posting an answer as I haven't tried with more components and stuff
– Al-un
Mar 10 at 18:50
add a comment |
0
active
oldest
votes
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%2f54000419%2fconflicting-eslint-config-using-typescript-and-prettier-in-a-nuxt-project%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f54000419%2fconflicting-eslint-config-using-typescript-and-prettier-in-a-nuxt-project%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
Are you using nuxt 2.4.0?
– Al-un
Mar 9 at 19:42
For what it is worth, I am also trying NuxtTS+ESLint. Here is my eslintrc. I am not posting an answer as I haven't tried with more components and stuff
– Al-un
Mar 10 at 18:50