Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange error "Unable to resolve path" during creating app with vue ui #1555

Closed
Smekalin opened this issue Jun 12, 2018 · 3 comments
Closed

Comments

@Smekalin
Copy link

Smekalin commented Jun 12, 2018

Version

3.0.0-beta.15

Reproduction link

https://github.com/smekalin/test_babel_unit_linter

Steps to reproduce

  1. Write
     vue ui 
    in console
  2. Create new project
  3. Select npm package
  4. Manually select features
  5. Select babel, Linter and Unit testing
  6. Next step select: ESLint Airbnb config, Lint on save, Mocha Chai
  7. Click to create project

What is expected?

There are no errors during application creation.

What is actually happening?

⠋  Running completion hooks...error: Unable to resolve path to module '@/components/HelloWorld.vue' (import/no-unresolved) at test/tests/unit/HelloWorld.spec.js:3:24:
  1 | import { expect } from 'chai';
  2 | import { shallowMount } from '@vue/test-utils';
> 3 | import HelloWorld from '@/components/HelloWorld.vue';
    |                        ^
  4 | 
  5 | describe('HelloWorld.vue', () => {
  6 |   it('renders props.msg when passed', () => {

1 error found.


I investigated it and have found as to reproduce it:
If I select Unit testing and Linter without Babel all is ok. If I select Unit testing, Linter, Babel I get error.

I receive a error, but the application and unit tests works.

I'm using:

  • macbook with High Sierra 10.13.5
  • npm 5.6.0
@thejprice
Copy link

I can confirm this is happening to me as well.

@Akryum Akryum closed this as completed in dc2f8e8 Jun 14, 2018
@jp-sauve
Copy link

jp-sauve commented Jun 20, 2018

and me! It still says "running completion hooks" so I don't know whether it is stuck or still going.
edit: sorry, I didn't see fix. I'm using 3.0.0-rc.3 should I not have this fix, since that's the branch to which it was comitted?

@Akryum
Copy link
Member

Akryum commented Jun 20, 2018

@jp-sauve This issue was fixed and closed a week ago. Please open a new issue with all the details necessary to understand your issue and to reproduce it.

@vuejs vuejs locked as resolved and limited conversation to collaborators Jun 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants