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

[@vueuse useStorage] Lost data in localStorage when I refresh the page? dev normal. after build deploy error. #422

Open
5 of 7 tasks
whoooami opened this issue Oct 14, 2024 · 0 comments

Comments

@whoooami
Copy link

whoooami commented Oct 14, 2024

Describe the bug

When I login in my home page.
1、authStore.login(data); // checked the data was save in localStorage.
2、When I click refresh button of chrome. I see the "token" in localStorage change to empty string.

When I run "vite --port 3000 --open" in local. the token is ok.
But When I run "vite-ssg build" and deploy to server. the token is missing when I refresh page.

I tried add ssr, but it still doesn't work.

ssr: {
    noExternal: ['@vueuse/core'], // 确保依赖正常工作
  },
import { useStorage } from '@vueuse/core'

export const useAuthStore = defineStore('auth', () => {
  const token = useStorage('token', '');

  const login = (user: any) => {
    const { token: newToken, ...userData } = user
    token.value = newToken
  }

  return {
    token,
    login,
  }
})

Reproduction

1、open it. use chrome dev tools. set localStorage token anything in application.
2、refresh page. the token value is gone.
tips: dev fine. build deploy to server, lost token.
reproduction project.

System Info

npm: 21.1.0
pnpm: 9.11.0

Used Package Manager

pnpm

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.

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
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