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

🐛 [Bug]: Error running litecart for the first time #148

Closed
3 tasks done
chr15m opened this issue Jul 29, 2024 · 2 comments
Closed
3 tasks done

🐛 [Bug]: Error running litecart for the first time #148

chr15m opened this issue Jul 29, 2024 · 2 comments
Labels
☢️ Bug Something isn't working

Comments

@chr15m
Copy link

chr15m commented Jul 29, 2024

Bug Description

After init and serve and visiting localhost:8000 I saw a blank page and the following in the developer console of my browser:

21:45:04.189 Uncaught Error: Extension Error: The validator 'all' must be a function.
    Zn http://localhost:8080/_/assets/vee-validate-usGg8cAm.js:5
    $t http://localhost:8080/_/assets/vee-validate-usGg8cAm.js:5
    <anonymous> http://localhost:8080/_/assets/index-BETTTWNd.js:2
    <anonymous> http://localhost:8080/_/assets/index-BETTTWNd.js:2

How to Reproduce

  • Downloaded the litecart binary for my platform.
  • Ran litecart init and it created the dirs.
  • Ran litecart serve and it ran successfully.
  • Then I tried to visit localhost:8080 and I was met with a blank page.
  • I looked at the web developer console and saw the error.

Expected Behavior

Litecart should start and present me with the first page.

litecart Version

litecart version LiteCart v0.1.11 (453b7e4) from 2024-07-07

Code Snippet (optional)

No response

Checklist:

  • I agree to follow litecart's Code of Conduct.
  • I have checked for existing issues that describe my problem prior to opening this one.
  • I understand that improperly formatted bug reports may be closed without explanation.
@chr15m chr15m added the ☢️ Bug Something isn't working label Jul 29, 2024
@shurco
Copy link
Owner

shurco commented Jul 30, 2024

Hi @chr15m
I rolled out a new version (v0.1.12) where this issue has been fixed. Thanks for the fix @kaichaosun (0f36efc)

@chr15m
Copy link
Author

chr15m commented Jul 30, 2024

Fixed, thanks.

@chr15m chr15m closed this as completed Jul 30, 2024
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