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

feat: using rolldown vite #1

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

feat: using rolldown vite #1

wants to merge 1 commit into from

Conversation

underfin
Copy link
Collaborator

@underfin underfin commented Jul 15, 2024

Test Status

Playground Name Dev Build Resons
ssr-vue
tailwind - -
vue -
vue-asset-base -
vue-jsx -
vue-legacy pending support system format
vue-lib
vue-server-origin -
vue-sourcemap -

@underfin underfin marked this pull request as draft July 15, 2024 06:14
@underfin underfin force-pushed the using-rolldown-vite branch from 0be1db9 to 9b49584 Compare December 6, 2024 08:58
@underfin
Copy link
Collaborator Author

@hi-ogawa the ssr-vue test sometimes has unexpected IPC resolve at vitest, I'm not idea to resolve it, could you help me take a look :)

@hi-ogawa
Copy link
Member

This looks like a revival of vitejs/vite#17760. Since Vitest still uses Vite 5 and I can see [email protected] in lockfile, so the issue came back. Either we manually set fs.cachedChecks: false like this:

// in vitest.config.e2e.ts
export default defineConfig({
  ...
  server: {
    fs: {
      cachedChecks: false,
    }
  },
})

or we should bump dep [email protected]. pnpm dedupe didn't work for me, but reinstalling by pnpm remove vitest && pnpm add -D -w vitest got a clean dep [email protected].

@underfin
Copy link
Collaborator Author

Ok. Thank you a lot!

@underfin underfin force-pushed the using-rolldown-vite branch 2 times, most recently from a69ee49 to 584c601 Compare December 19, 2024 05:47
@underfin underfin force-pushed the using-rolldown-vite branch from 584c601 to c794c24 Compare December 19, 2024 05:51
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

Successfully merging this pull request may close these issues.

2 participants