RollupError: "Fragment" is not exported when updating to @vueuse/core 10.x

[Santobert]

Describe the bug

In our CI environment the following error occurs during vite build:

"Fragment" is not exported by "node_modules/@vueuse/core/node_modules/vue-demi/lib/index.mjs", imported by "node_modules/@vueuse/core/index.mjs".
file: /builds/.../node_modules/@vueuse/core/index.mjs:3:135
1: import { noop, makeDestructurable, toValue, isClient, tryOnScopeDispose, isIOS, tryOnMounted, computedWithControl, isObject, objectOmit, promiseT...
2: export * from '@vueuse/shared';
3: import { isRef, ref, shallowRef, watchEffect, computed, inject, isVue3, version, defineComponent, h, TransitionGroup, shallowReactive, Fragment, ...
                                                                                                                                          ^
4: 
5: function computedAsync(evaluationCallback, initialState, optionsOrRef) {
error during build:
RollupError: "Fragment" is not exported by "node_modules/@vueuse/core/node_modules/vue-demi/lib/index.mjs", imported by "node_modules/@vueuse/core/index.mjs".

What seems odd to me is that the error message says it could not import from vue-demi/lib/index.mjs, but actually it should import from vue-demi/lib/v2.7/index.mjs.

Reproduction

System Info

System:
    OS: Linux 5.4 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (1) x64 Intel(R) Xeon(R) CPU @ 2.30GHz
    Memory: 2.85 GB / 3.60 GB
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 18.16.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.5.1 - /usr/local/bin/npm
  npmPackages:
    @vueuse/core: 10.0.2 => 10.0.2 
    vue: 2.7.14 => 2.7.14

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a VueUse issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[antfu]

We temporarily close this due to the lack of enough information.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required

[Santobert]

Funnily enough, the problem is due to a misconfigured gitlab-ci cache. I wonder if the cause of this issue is related to #2972 and was cached at that moment and therefore occurred from then on.

I'm writing this in case anyone else has this problem too

[jschirrmacher]

How did you solve this "misconfigured gitlab-ci cache" problem, @Santobert ?
I have exactly the same error message.

[Santobert]

Previously I had cached the node_modules directory with ${CI_COMMIT_REF_SLUG} as the key. I solved the problem by using the example from the official documentation: https://docs.gitlab.com/ee/ci/caching/#cache-nodejs-dependencies