-
Notifications
You must be signed in to change notification settings - Fork 5
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
@morpheme/nuxt package no longer installs #199
Comments
The same happens when using this |
Hi, sorry for the inconvenience and thanks for the report. Do you mind create a minimal reproduction using stackblitz or share a repo so that I can check it out. |
Can you try upgrade to version |
Hey, thanks for getting back. The terminal says: |
Hi, I think this package does not support Yarn 4 yet. I suggest you install it with PNPM or NPM. |
I see. is it something different from the .rc ones? those worked well with Yarn 4 |
I think no much different with the RC one. After some digging, I think this is caused by circular dependency. Let me check and try to fix it. |
Hi, can you try version |
Progress. The packages install but when starting there's a new error:
|
Okay. Try version |
Tried it now, getting the previous error: |
Environment
Darwin
v20.9.0
3.12.4
3.12.0
2.9.7
[email protected]
vite
runtimeConfig
,devServer
,modules
,piniaPersistedstate
,auth
,css
,typescript
,build
,builder
,ssr
,morpheme
,watchers
,ignore
,devtools
,experimental
,compatibilityDate
@morpheme/[email protected]
,@nuxtjs/[email protected]
,@sidebase/[email protected]
,@vueuse/[email protected]
,@pinia/[email protected]
,[email protected]
,@pinia-plugin-persistedstate/[email protected]
-
Reproduction
Running
yarn install
after the last git update on@morpheme/nuxt
Describe the bug
Running
yarn install
now throws this error:Additional context
Everything worked on until 2 days ago. Wanted a fresh install so cleaned
node_modules
and ranyarn install
.Excluded each package one by one and found out it's
@morpheme/nuxt
that causes the memory leak.Reverting to an earlier
yarn.lock
allows the packages to be installed and the build to run, however it does not solve the problem.Logs
The text was updated successfully, but these errors were encountered: