-
-
Couldn't load subscription status.
- Fork 6.3k
Closed
Labels
Description
Version
3.5.5
Environment info
Environment Info:
System:
OS: Windows 7
CPU: (4) x64 Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Binaries:
Node: 11.14.0 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.7.0 - C:\Program Files\nodejs\npm.CMD
npmGlobalPackages:
@vue/cli: Not Found
Steps to reproduce
- Run in command line:
vue create vue-test - Manually select features
- Make sure "Linter / Formatter" is selected
- Pick "ESLint Airbnb config"
- "Lint on save"
- Select to place config "In dedicated config files"
- Do not save preset for future use
What is expected?
Project will be created without errors.
What is actually happening?
ERROR TypeError: (0 , _ignore.getFileExtensions) is not a function
Occurred while linting d:\temp\vue-test\src\App.vue:9
TypeError: (0 , _ignore.getFileExtensions) is not a function
Occurred while linting d:\temp\vue-test\src\App.vue:9
at checkSourceValue (d:\temp\vue-test\node_modules\eslint-plugin-import\lib\
rules\no-useless-path-segments.js:103:60)
at checkSourceValue (d:\temp\vue-test\node_modules\eslint-module-utils\modul
eVisitor.js:29:5)
at checkSource (d:\temp\vue-test\node_modules\eslint-module-utils\moduleVisi
tor.js:34:5)
at listeners.(anonymous function).forEach.listener (d:\temp\vue-test\node_mo
dules\eslint\lib\util\safe-emitter.js:45:58)
at Array.forEach (<anonymous>)
at Object.emit (d:\temp\vue-test\node_modules\eslint\lib\util\safe-emitter.j
s:45:38)
at NodeEventGenerator.applySelector (d:\temp\vue-test\node_modules\eslint\li
b\util\node-event-generator.js:251:26)
at NodeEventGenerator.applySelectors (d:\temp\vue-test\node_modules\eslint\l
ib\util\node-event-generator.js:280:22)
at NodeEventGenerator.enterNode (d:\temp\vue-test\node_modules\eslint\lib\ut
il\node-event-generator.js:294:14)
at CodePathAnalyzer.enterNode (d:\temp\vue-test\node_modules\eslint\lib\code
-path-analysis\code-path-analyzer.js:632:23)
Using "ESLint with error prevention only" or "ESLint Standard config" works correctly without errors. Earlier vue-cli versions did not have this problem, but I didn't have time to find exact version where this issue started.
deanpienaar, rreckonerr, vanyadymousky, TimoBechtel, bumgle and 5 more