-
-
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
vue-cli-service build fails due to wrong filename since v3.10.0 #4667
Comments
Ok, I tracked the issue down to the following commit: When I remove this commit, |
hey @RSeidelsohn can i work on this? |
Sure, I'd be happy. I would love to do it myself, but I so far do not find the time to dig into the details of why that commit was done and how to not break the functionality it introduced (if at all) and how to fix the issue with the filenames I have. |
I can tell you what the feature of the commit was, it's to correctly parse the name of the file without query string when in the config it's defined as [name].js?v=xxx I don't know if it's really a useful feature though So instead of url.parse() you could Eg: assets = assets
.map(a => {
a.name = a.name.split("?")[0]
return a
}) |
|
Pull request #4809 has been accepted and fixes this issue. |
… (#4809) * fix(lib): replace "url" module with simple string split (close #4667) Fixes issue #4667 by implementing the proposal vuejs/vue-cli#4667 (comment) Also gets rid of a node module by using simpler code for removing eventual GET parameters * Update packages/@vue/cli-service/lib/commands/build/formatStats.js Co-Authored-By: Haoqun Jiang <haoqunjiang@gmail.com>
… (#4809) * fix(lib): replace "url" module with simple string split (close #4667) Fixes issue #4667 by implementing the proposal vuejs/vue-cli#4667 (comment) Also gets rid of a node module by using simpler code for removing eventual GET parameters * Update packages/@vue/cli-service/lib/commands/build/formatStats.js Co-Authored-By: Haoqun Jiang <haoqunjiang@gmail.com>
Version
4.0.5
Reproduction link
cli-service-bug-reproduction
Environment info
Steps to reproduce
run "yarn build"
What is expected?
Build runs through
What is actually happening?
Command fails with exit code 1 because one file created can not be accessed:
"Error: ENOENT: no such file or directory, open '/your/path/here/dist/js/article%20page0.852bf769.js'" - the file exists, but the space between "article" and "page15" has to be escaped or written as space, not as "%20". The file system can not find it with the percent sign. This happens also on a MacBook of a colleague.
I tracked the bug down to cli-service version 3.10.0 - up to 3.9.3 the build is fine, from version 3.10.0 on all versions until 4.0.5 fail with the exact same error.
I might be allowed to send a copy of the repo affected to one dev for debugging purposes.I have created a completely stripped down version of our repository that should enable everyone to reproduce the bug. See link in the top section.The text was updated successfully, but these errors were encountered: