-
Notifications
You must be signed in to change notification settings - Fork 916
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
Failed to build for missing descriptor.scriptCompiled
inside selectBlock
#1723
Comments
Do you have a reproduction? Like, what's in the |
I believe it's about race condition. I've reduced App.vue to minimum and the issue still sometimes occurs. I don't find a way to reproduce it stably. I awared that possibility of occurrence is relative to cpu load. The lower cpu load is, the higher possibility is. It hasn't been confirmed. I'm working on it. |
I can't confirm the cpu load theory which I mentioned above. And I found that not only my app but also the original one created by vue-cli without any modification will occur the issue when running build with `vue create app` → `cd app` → `npm run build` → FAIL
And a screenrecord of the above actions is here. In the video I demonstrate how the build went wrong again and again, then suddenly turn to success without any changes. |
I'm also experiencing this after upgrading an app to Vue 3 with using script setup. Happens for view components. Some views are added directly to route record's component property, but many routes are async loaded like: {
path: '/',
name: 'home',
component: (): Promise<Component> => import(/* webpackChunkName: "solo" */ '@/views/index.vue') as unknown as Promise<Component>,
}, |
Happens only when doing production build |
I've added this paragraph to the release note:
I'm sorry for the inconvenience. |
@sodatea setting parallel to false does not work for me, thus I'm unable to build for production. |
Interesting - I'm not experiencing this issue anymore. I don't think I've upgraded any package that could have affected this or done any major changes as the problem appeared for a whole bunch of components, however, I did nuke |
I have been scratching my head at this for days and found this thread from the comment in vue loader source. I am dual booting on my pc and my build works in windows10 but not in linux (manjaro). The current fix in place doesn't always fix the issue. https://github.com/vuejs/vue-loader/blob/next/src/select.ts line 28 if the component has I have this issue every time i build in my linux environment (it works in my ubuntu based CI/CD pipelines) I can clear node_modules and package-lock.json and reinstall and still have the problem. If there is anything need to troubleshoot this, i am more that happy to help. EDIT. just ran a cpu stress test and ran a few builds and every single one of them completed successfully. (I cleared the webpack cache-loader between each build to make sure it didn't pull the cached version). when i turned the stress test off, they all failed. CPU is an Intel 6700k |
- new `<script setup>` vuejs/rfcs#227 - new `<style>` variable injection vuejs/rfcs#231 Requires a version of `@vue/compiler-sfc` that supports the above features. Also should fix #1723
Should have been fixed in v16.0.0 |
Version
16.0.0-beta.6
Steps to reproduce
node_modules/@vue/cli-service/node_modules/vue-loader-v16
I found that
selectBlock
is invoked whiledescriptor.scriptCompiled
have not been assigned. No more idea about the issue.vue-loader/src/index.ts
Lines 105 to 108 in f19f2b3
vue-loader/src/index.ts
Line 134 in f19f2b3
vue-loader/src/select.ts
Lines 25 to 29 in f19f2b3
What is expected?
Build success
What is actually happening?
Build failed
The text was updated successfully, but these errors were encountered: