-
-
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
webpack-dev-server 3.8 broken on windows 10 #4424
Comments
Can't reproduce. Please provide a reproduction repo. And, what file system are you on? What's your project path (run |
pwd = c:\dev\some-repo (ntfs filesystem, nothing special) Doesn't need a repo, i just created the app from vue-cli with nothing in it (vue cli did the npm install) |
oh no, don't tell me it's because of my "dev" folder :D |
It's the pwd thing ! i just did the project in another folder and it works flawlessly :o |
False-positive in https://github.com/sindresorhus/is-absolute-url (webpack-dev-server changed from testing Please report to that repository. I believe it's because of the lower case |
I removed space from the parent folder name and it worked without problem |
Windows uses case insensitive path. |
maybe vue-cli should downgrade the version of webpack-dev-server 3.8 to 3.7.2 until it's fixed in is-absolute-url ? |
I found that VS Code debug launcher start node.exe with working folder which has lower case volume label. I used ProcessHacker to inspect the process property of node.exe, and found when the Current Directory was 'e:/abc/proj', the issue happened, when is was 'E:/abc/proj', it was ok. |
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.
Version
3.10.0
Reproduction link
[npm run serve](npm run serve)
Environment info
Steps to reproduce
"npm run serve" on newly create project with "vue create" (default options)
What is expected?
'npm run serve' should work
What is actually happening?
'npm run serve' give this error:
INFO Starting development server...
10% building 2/2 modules 0 active ERROR Error: Watching remote files is not supported.
Error: Watching remote files is not supported.
at Server.setupWatchStaticFeature
"it worked last time !"
The text was updated successfully, but these errors were encountered: