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

fastest-levenshtein error #243

Open
hmz22 opened this issue Jul 27, 2022 · 0 comments · May be fixed by #248
Open

fastest-levenshtein error #243

hmz22 opened this issue Jul 27, 2022 · 0 comments · May be fixed by #248
Assignees
Labels
bug Something isn't working Under Review PR status is under review

Comments

@hmz22
Copy link

hmz22 commented Jul 27, 2022

Describe the bug

✘ [ERROR] [plugin vite:dep-pre-bundle] Failed to resolve entry for package "fastest-levenshtein". The package may have incorrect main/module/exports specified in its package.json.

    node_modules/@persian-tools/persian-tools/build/persian-tools.esm.js:1:24:
      1 │ import{closest as e}from"fastest-levenshtein";var t=["۰","۱","۲","۳","۴","۵","۶","۷","۸","۹"],o=...
        ╵                         ~~~~~~~~~~~~~~~~~~~~~

To Reproduce
Steps to reproduce the behavior:
See error when install and run.
you used fastest-levenshtein@1.0.12 but after install your package fastest-levenshtein install with 1.0.14

Expected behavior

in your package.json I see

...
  "dependencies": {
    "fastest-levenshtein": "^1.0.12"
  },
...

I think you must exact install version 1.0.12

...
  "dependencies": {
    "fastest-levenshtein": "1.0.12"
  },
...

Desktop (please complete the following information):

  • OS: windows 11
  • Browser chrome
  • Version 103.0.5060.134
@ali-master ali-master added bug Something isn't working Under Review PR status is under review labels Jul 28, 2022
@ali-master ali-master self-assigned this Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Under Review PR status is under review
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants