-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
After start vue-cli-3 tutorial project 98% after emitting CopyPlugin #4174
Comments
Please provide an actual reproduction repo. |
I'm sorry but I can't reproduce this issue on my machine. |
@sodatea yes man, I tried run on virtual machine and everything is ok, sorry for for request |
I'm getting the same |
Me too:
and that's it. No response. |
I experienced the same issue when I tried to use
, i.e. I forgot to specify the package to import from. |
I have the same problem, but after debugging I found a mistake from my router file. |
I had such a problem. Somewhere in the code I left an empty import and forgot. Code:
Hope this can help you |
I was getting this problem too, but for me it was defining a route in the routes (vue-router) but without creating the view component, it just hung out. |
I got the same error message, but I resolved it. The problem is all import paths are case sensitive! For example, if your import like below: |
closes vuejs#2547 closes vuejs#5032 I'm still very hesitant on adding this feature, though. First, this change allows project creation in a folder with uppercase letters in its name. It is strongly discouraged and may cause many weird issues all over the ecosystem. For example, vuejs#5022, vuejs#4424, vuejs#3665, vuejs#4174#issuecomment-569709494 are all caused by case issues. Adding support for uppercase project names will only worsen this situation. Secondly, it adds a lot of maintenance burden to us. As noted in the comments, these prompts are hard to test right now (because `createTestProject` runs in another process so it's hard to intercept the prompts). Even if such test utilities are added in the future, it's still very tedious to take care of all the case issues in the test suite. What's worse is that we can affect the project folders created by @vue/cli by converting the project name to lower case. But for `vue create .`, we cannot change the current folder's name. So, we'll have another edge case to test.
I had this problem because of an empty import ( |
Very Very Tnks ! |
thanks man haha |
I think you forget to copy the files that starts with '.' like: .env or .eslint |
I have same problem stuck in 98%. 98% after emitting CopyPlugin In my case, I recheck again my code, and I found my import path is invalid, something like :
After fix the code, It works again. |
There was same error for me, the problem is that I lost my vue.config.js file. |
我也遇到了同样的问题,已经排除了 |
@YoungHearts 看看是不是vue.config.js丢失了,我是误删了。 |
maybe your import path is invalid like: import { getPDF } from '' |
I had the same problem. Turns out one of my imports was |
require(‘’) |
I also encountered this problem. |
This problem will occur as long as the path of import is written wrong. I don't know what happened, it was fine before |
Delete the code, re-pull the code, reinstall vscode, problem solved |
Version
3.8.4
Environment info
Steps to reproduce
Download Nodejs version 10.16.0 , install, npm install -g @vue/cli , vue create hello-world , npm run serve
What is expected?
project is compiled
What is actually happening?
INFO Starting development server...
98% after emitting CopyPlugin
The text was updated successfully, but these errors were encountered: