Skip to content
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

Dependency warning in workspace+pnpm environment. #2381

Closed
Tracked by #770
akiot-b opened this issue Oct 18, 2023 · 0 comments · Fixed by nuxt-modules/mdc#160 or #2583
Closed
Tracked by #770

Dependency warning in workspace+pnpm environment. #2381

akiot-b opened this issue Oct 18, 2023 · 0 comments · Fixed by nuxt-modules/mdc#160 or #2583

Comments

@akiot-b
Copy link

akiot-b commented Oct 18, 2023

Environment


  • Operating System: Linux
  • Node Version: v18.17.0
  • Nuxt Version: 3.7.4
  • CLI Version: 3.9.0
  • Nitro Version: -
  • Package Manager: pnpm@8.6.12
  • Builder: -
  • User Config: devtools, modules
  • Runtime Modules: @nuxt/content@2.8.5
  • Build Modules: -

Reproduction

https://github.com/akiot-b/issue-20231018.git

Describe the bug

nuxt no longer requires 'shamefully-hoist=true' in workspace+pnpm as of 3.7.4.
Currently, @nuxt/content warns without 'shamefully-hoist'.

pnpm support without --shamefully-hoist #14146

By the way, if you use npm, you will not get any warning.

pnpm install
cd nuxt
pnpm dev
 WARN  Failed to resolve dependency: slugify, present in 'optimizeDeps.include'      
 WARN  Failed to resolve dependency: is-buffer, present in 'optimizeDeps.include'    
 WARN  Failed to resolve dependency: debug, present in 'optimizeDeps.include'        
 WARN  Failed to resolve dependency: flat, present in 'optimizeDeps.include'         
 WARN  Failed to resolve dependency: node-emoji, present in 'optimizeDeps.include'   
 WARN  Failed to resolve dependency: extend, present in 'optimizeDeps.include'       
 WARN  Failed to resolve dependency: hast-util-raw, present in 'optimizeDeps.include'   

Additional context

No response

Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant