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.

No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future.

See original GitHub issue

Version

3.3.0

Reproduction link

https://github.com/410919244/mp-web.git

Environment info

Environment Info:

  System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
  Binaries:
    Node: 11.7.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.13.0 - C:\word\yarn\bin\yarn.CMD
    npm: 6.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 38.14393.2068.0
  npmPackages:
    vue: ^2.5.2 => 2.5.16
    vue-hot-reload-api: ^2.2.4 => 2.3.0
    vue-html-loader: ^1.2.3 => 1.2.4
    vue-loader: ^13.5.0 => 13.7.1
    vue-router: ^3.0.1 => 3.0.1
    vue-style-loader: ^3.0.3 => 3.1.2
    vue-template-compiler: ^2.2.1 => 2.5.16
    vue-template-es2015-compiler:  1.6.0
    vuex: ^2.2.1 => 2.5.0
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

yarn install yarn run serve

What is expected?

100%

What is actually happening?

No parser and no filepath given, using ‘babel’ the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be inferred. 65% building 866/940 modules 74 active …les\vux\src\components\sticky\index.vue No parser and no filepath given, using ‘babel’ the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be inferred. 65% building 869/940 modules 71 active …les\vux\src\components\sticky\index.vue

The error message should be that there is a problem in the configuration. There is no solution on the internet. My technical ability can not solve this problem.