-
Notifications
You must be signed in to change notification settings - Fork 156
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
Please remove dependency on deasync #403
Comments
Hi! I think this is related to @vue/cli-plugin-unit-jest, not vue-jest: vuejs/vue-cli#6445 |
|
I feel that Vue CLI should be installing the correct versions of dependencies. Why does |
For Vue3 I modify the script a bit. In my case I'm using typescript, if your project don't need that then remove ts-jest, what I changed here is @vue/vue3-jest Hope this help! |
Thank you very much. You saved my day!! |
|
vuejs/vue-jest#403 (comment) For Vue2: ``` npm install --save-dev @vue/cli-plugin-unit-jest@next @vue/vue2-jest jest ``` For Vue3: ``` npm install --save-dev @vue/cli-plugin-unit-jest@next @vue/vue3-jest jest ts-jest ```
vuejs/vue-jest#403 (comment) For Vue2: ``` npm install --save-dev @vue/cli-plugin-unit-jest@next @vue/vue2-jest jest ``` For Vue3: ``` npm install --save-dev @vue/cli-plugin-unit-jest@next @vue/vue3-jest jest ts-jest ```
vuejs/vue-jest#403 (comment) For Vue2: ``` npm install --save-dev @vue/cli-plugin-unit-jest@next @vue/vue2-jest jest ``` For Vue3: ``` npm install --save-dev @vue/cli-plugin-unit-jest@next @vue/vue3-jest jest ts-jest ```
Out of nowhere, since trying out Node 16 and Node 17,
npm install
fails because ofdeasync
.I can see that
deasync
is a dependency ofvue-jest
:The reason for this issue is that for whatever reason the
deasync
library has dependencies on some nasty Python and Node GYP stuff. Why this is only a problem now with Node 16 and Node 17 I don't know, but it's starting to cause a big problem for Vue CLI users upgrading to the current version of Node. We are stuck on Node 14 LTS.Given the LTS will eventually be deprecated, every user of Vue CLI/vue-jest is going to encounter this problem soon.
I am sure I'm not alone in thinking it's pretty ridiculous needing Python installed purely for the sake of that poorly maintained library. Especially if a developer has no other need of Python.
(As for why
npm install
needs to run a C++ compiler via Python, rather than just having the binary on npm, that's a whole other topic...)The text was updated successfully, but these errors were encountered: