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

Adding ClientOnly to any part of the App.Vue gives an empty error #396

Open
5 tasks done
rezelute opened this issue Apr 18, 2024 · 0 comments
Open
5 tasks done

Adding ClientOnly to any part of the App.Vue gives an empty error #396

rezelute opened this issue Apr 18, 2024 · 0 comments

Comments

@rezelute
Copy link

rezelute commented Apr 18, 2024

Describe the bug

What im trying to do:
I only want to pre-render for the purpose of social media previews (unfurling) but Im unable to wrap everything in the App template with ClientOnly. But then I also tried to wrap anything in ClientOnly in App.Vue and I also get an error when trying to build:

<template>
   <div>
      <RouterView />

      <ClientOnly>
         <p>test</p>
      </ClientOnly>
   </div>
</template>

The error:

[vite-ssg] An internal error occurred.
[vite-ssg] Please report an issue, if none already exists: https://github.com/antfu/vite-ssg/issues
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: ENOTEMPTY: directory not empty, rmdir 'C:\...\.vite-ssg-temp\ze9v78zw2v\assets'] {
  errno: -4051,
  code: 'ENOTEMPTY',
  syscall: 'rmdir',
  path: 'C:\\...\\.vite-ssg-temp\\ze9v78zw2v\\assets'
}
node:child_process:935
    throw err;

Reproduction

in describe bug

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
    Memory: 11.51 GB / 31.92 GB
  Binaries:
    Node: 16.20.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.19.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (123.0.2420.97)

Used Package Manager

npm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant