pinia: Not able to use pinia: No matching export in "node_modules/pinia/node_modules/vue-demi/lib/index.mjs" for import "hasInjectionContext"
Reproduction
https://github.com/shree-c/mock_two_test_pinia
Steps to reproduce the bug
Expected behavior
I am doing basic activity such as creating a store and importing it into a component.
Actual behavior
Vite not able to build both for dev and prod.
I am getting the following error on vite terminal:
No matching export in "node_modules/pinia/node_modules/vue-demi/lib/index.mjs" for import "hasInjectionContext"
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 3
- Comments: 16 (2 by maintainers)
You need to update vue to 3.3. I should have set the peer dep…
For me, work update to vue 3.3.4
The fix for a fresh vite + vue 2.7 app was to downgrade pinia from 2.1.7 to 2.0.x. Seems there was some regression in the dependency chain. Hope this helps the next person that sees this GitHub issue in the search results trying to troubleshoot this problem and hopefully this issue will be resolved in a future version of pinia.
if you use uni-app, it’s inner vue version is 3.2.47. we must be use pinia 2.0.x
“hasInjectionContext” is not exported by “node_modules/.pnpm/pinia@2.1.1_typescript@5.0.4+vue@3.3.3/node_modules/vue-demi/lib/index.mjs”, imported by “node_modules/.pnpm/pinia@2.1.1_typescript@5.0.4+vue@3.3.3/node_modules/pinia/dist/pinia.mjs”.
Argg… had to downgrade to 2.0.35 because of this bug. @posva There are a lot of 2.7 installations in the field. Upgrading to vue 3.x is very often not possible. So to others with the same problem: Vue 2.7 only works with Pinia 2.0.35 (and below???, not tested)
Fix for vue-demi build issue with PNPM in GitHub Actions
If you’re getting this error during pnpm build:
export 'hasInjectionContext' was not found in 'vue-demi'And PNPM shows a warning about ignored build scripts, the issue is that PNPM is blocking vue-demi’s build script, preventing it from properly detecting Vue 2 or Vue 3.
Solution: Add this step before your build in GitHub Actions:
This will allow vue-demi to execute its required setup and fix the issue. 🚀
@shree-c @shunyue1320 hey guys, any updated? i have the same issue while migrating from vue-cli to vite