Problems with vite
See original GitHub issueDo not know how to load path pockebase
On solid-start-0.2.5, with SSR and without SSR enabled
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Issues · vitejs/vite - GitHub
Contribute to vitejs/vite development by creating an account on GitHub. ... [Hard Issue] vite should not change importmap position in index.html pending ...
Read more >Troubleshooting - Vite
Vite cannot handle and does not support code that only runs on non-strict mode (sloppy mode). This is because Vite uses ESM and...
Read more >Troubleshooting | Vite Ruby
This section lists a few common gotchas, and bugs introduced in the past. Please skim through before opening an issue. Installation Problems #....
Read more >Troubleshooting - Laravel Vite
Here are solutions to common problems encountered with either Vite or Laravel Vite. If you encounter an issue that is not mentionned here,...
Read more >Vite JS - Created to perform - collective:mind | DEV
Why Vite? The Problems. Currently, JavaScript-based tooling is starting to hit performance bottleneck. It often takes an unreasonably long ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@DivyanshuBhoyar
I’m not sure what is the reason for the error and as mentioned previously I cannot reproduce it with the starter template (aka.
npm init solid).Make sure that the PocketBase JS SDK was instanlled by checking if there is a
pocketbasefolder inside yournode_modules(also you can use the latest PocketBase 0.8.0 release).Also make sure that the PocketBase binary is not placed inside the
src/routes/directory, because depending how your node resolver is configured it is also possible thatimport PocketBase from "pocketbase"will try to load the binary instead of the node module.As an alternative you can also start from scratch and try to reproduce the error by initializing new starter template (aka.
npm init solid).Thanks @ganigeorgiev Renaming pocketbase binary to pocketbase-bin seems to have solved the problem with same code.