Describe the bug
In the @nuxt/typescript-runtime code here it references either @nuxt/cli or @nuxt/cli-edge but these are dependencies of nuxt, not @nuxt/typescript-runtime. normally this shouldn't be an issue because you'd have nuxt installed as well but with the latest npm workspaces it seems to want to hoist this package (@nuxt/typescript-runtime) but not nuxt or its dependency @nuxt/cli. this causes a module resolution error when running nuxt-ts
To Reproduce
- include
nuxt, @nuxt/typescript-runtime, and @nuxt/typescript-build as dependencies of your sub-package in a monorepo.
- install dependencies at root using
npm install with workspaces configured.
- try to run sub-package using
nuxt-ts
Expected behavior
nuxt-ts should run successfully. but depending on how the packages are hoisted it's possible that it won't find @nuxt/cli and @nuxt/cli-edge and crash.
Describe the bug
In the
@nuxt/typescript-runtimecode here it references either@nuxt/clior@nuxt/cli-edgebut these are dependencies ofnuxt, not@nuxt/typescript-runtime. normally this shouldn't be an issue because you'd havenuxtinstalled as well but with the latest npm workspaces it seems to want to hoist this package (@nuxt/typescript-runtime) but notnuxtor its dependency@nuxt/cli. this causes a module resolution error when runningnuxt-tsTo Reproduce
nuxt,@nuxt/typescript-runtime, and@nuxt/typescript-buildas dependencies of your sub-package in a monorepo.npm installwith workspaces configured.nuxt-tsExpected behavior
nuxt-tsshould run successfully. but depending on how the packages are hoisted it's possible that it won't find@nuxt/cliand@nuxt/cli-edgeand crash.