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

Local Search Provider Hash Changes Every Build #4246

Open
4 tasks done
wSedlacek opened this issue Oct 3, 2024 · 2 comments
Open
4 tasks done

Local Search Provider Hash Changes Every Build #4246

wSedlacek opened this issue Oct 3, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@wSedlacek
Copy link
Contributor

wSedlacek commented Oct 3, 2024

Describe the bug

When using the local search provider the hashes of the bundles will change every build.

Reproduction

Set search: { provider: 'local' } then build, note hash of @localSearchIndexroot, then build again, see hash changed.

Expected behavior

The @localSearchIndexroot hash should only change if the contents of the docs changed.

System Info

  System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 75.22 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.8 - /usr/local/bin/pnpm
    bun: 1.0.0 - ~/.bun/bin/bun
  Browsers:
    Safari: 17.6

Additional context

No response

Validations

@wSedlacek wSedlacek added the bug: pending triage Maybe a bug, waiting for confirmation label Oct 3, 2024
@brc-dd brc-dd added bug Something isn't working and removed bug: pending triage Maybe a bug, waiting for confirmation labels Oct 3, 2024
@brc-dd
Copy link
Member

brc-dd commented Oct 3, 2024

Does this work on macOS?

Yes it does. Looks like you ran it without npx in front. But anyway I can confirm the bug with latest version, no need for env info.

@wSedlacek
Copy link
Contributor Author

Yes it does. Looks like you ran it without npx in front. But anyway I can confirm the bug with latest version, no need for env info.

Hm, it worked when I retried. Seems like npx was behaving differently when I was using corepack and in a project directory, running it from the home directory resolved the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants