question-mark
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.

@vue/cli-plugin-eslint - Other ESLint CLI options are *not* also supported.

See original GitHub issue

Version

3.7.0

Environment info

Environment Info:

  System:
    OS: Linux 4.4 Ubuntu 16.04.6 LTS (Xenial Xerus)
    CPU: (8) x64 Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz
  Binaries:
    Node: 8.12.0 - ~/node-current/bin/node
    Yarn: 1.3.2 - ~/node-current/bin/yarn
    npm: 6.9.0 - ~/node-current/bin/npm
  Browsers:
    Chrome: 73.0.3683.75
    Firefox: 60.2.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0 
    @vue/babel-plugin-transform-vue-jsx:  1.0.0 
    @vue/babel-preset-app:  3.7.0 
    @vue/babel-preset-jsx:  1.0.0 
    @vue/babel-sugar-functional-vue:  1.0.0 
    @vue/babel-sugar-inject-h:  1.0.0 
    @vue/babel-sugar-v-model:  1.0.0 
    @vue/babel-sugar-v-on:  1.0.0 
    @vue/cli-overlay:  3.7.0 
    @vue/cli-plugin-babel: ^3.7.0 => 3.7.0 
    @vue/cli-plugin-e2e-cypress: ^3.7.0 => 3.7.0 
    @vue/cli-plugin-eslint: ^3.7.0 => 3.7.0 
    @vue/cli-plugin-pwa: ^3.7.0 => 3.7.0 
    @vue/cli-plugin-unit-jest: ^3.7.0 => 3.7.0 
    @vue/cli-service: ^3.7.0 => 3.7.0 
    @vue/cli-shared-utils:  3.7.0 
    @vue/component-compiler-utils:  2.6.0 
    @vue/devtools: ^1.1.0 => 1.1.0 
    @vue/eslint-config-standard: ^4.0.0 => 4.0.0 
    @vue/preload-webpack-plugin:  1.1.0 
    @vue/test-utils: ^1.0.0-beta.29 => 1.0.0-beta.29 
    @vue/web-component-wrapper:  1.2.0 
    eslint-plugin-vue:  4.7.1 
    jest-serializer-vue:  2.0.2 
    vue: ^2.6.10 => 2.6.10 
    vue-cli-plugin-quasar: ^1.0.0-beta.1 => 1.0.0-beta.1 
    vue-d3-network: ^0.1.109 => 0.1.109 
    vue-eslint-parser:  2.0.3 
    vue-hot-reload-api:  2.3.3 
    vue-jest:  3.0.4 
    vue-loader:  15.7.0 
    vue-masonry-css: ^1.0.2 => 1.0.3 
    vue-router: ^3.0.2 => 3.0.2 
    vue-server-renderer:  2.6.10 
    vue-split-panel: ^1.0.4 => 1.0.4 
    vue-style-loader:  4.1.2 
    vue-template-compiler: ^2.6.10 => 2.6.10 
    vue-template-es2015-compiler:  1.9.1 
    vuedraggable: ^2.20.0 => 2.20.0 
    vuelidate: ^0.7.4 => 0.7.4 
    vuex: ^3.1.0 => 3.1.0 
  npmGlobalPackages:
    @vue/cli: 3.5.5

Steps to reproduce

run vue-cli-service lint with extra options (ex: node ./node_modules/.bin/vue-cli-service lint -o report.json -f json)

What is expected?

Extra params would be proxied to eslint cli

What is actually happening?

No extra options are supported.

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:3
  • Comments:11 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
cjacksoncommented, May 23, 2019

We can specify --format on the vue-cli-service lint command. Is there a way to output the result to a file, similar to the -o option on the eslint CLI?

2reactions
LinusBorgcommented, Aug 1, 2019

As far as I understand now, it appears there’s no work around yet

I would say that running eslint directly is a totally fine workaroud. Even though lint.js seems to do a lot of stuff, most of that is about either

  • loading the config (which eslint cli does for you)
  • configuring the CLIEngine (which you also don’t have to when running eslint via cli directly)
  • setting some default folder and file globs to define what to lint

The latter can be done quickly by adding your own globs when running eslint via cli.

So in summary: The lint command itself doesn’t do much more than run eslint

Given that, and given that there are eslint options that only work with eslint CLI, not with eslint CLIEngine, I don’t think that it’s worth re-creating these options in our codebase, as it doesn’t take much to run eslint “manually” and use the options directly.

I think it would make more sense to document how to run eslint manually (with which globs etc) to make it work exactly like lint - then people can use that when they need to use eslint options that only work in the cli version.

Read more comments on GitHub >

github_iconTop Results From Across the Web

vue/cli-plugin-eslint
Start using @vue/cli-plugin-eslint in your project by running `npm i @vue/cli-plugin-eslint` ... Other ESLint CLI options are not supported.
Read more >
Command Line Interface
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >
@vue/cli-plugin-eslint | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >
How to disable ESLint in vue-cli?
I removed @vue/cli-plugin-eslint and now the command vue-cli-service serve says Error: Cannot find module '@vue/cli-plugin-eslint' . What else ...
Read more >
vue/cli-plugin-eslint - npm Package Health Analysis
All security vulnerabilities belong to production dependencies of direct and indirect packages. License: MIT. Security Policy: No.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found