build/doc: remind user to run Docker, regenerate broken package-lock.json, and upgrade incompatible supabase-js lib #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First off, thank you very much for kicking off this project! I'm just getting started building my own local stack on the web platform, so it's great to have more references available.
I bumped into a few issues while setting up this project, so I figured I'd share them here.
Problem
My Docker was not running when executing
supabase start
:Cannot connect to the Docker daemon at unix:///Users/itsuka/.docker/run/docker.sock. Is the docker daemon running?
Solution
I updated the readme to remind users to (install and) run Docker if not running already.
Problem
I ran into the following error when executing
node src/scripts/indexBlogLocal.mjs
:I'm no expert when it comes to the JS build system. All I understand is that
npm install
script should create a build output atnode_modules/sharp/build/Release/
. But for some reason, it's not happening in my case. Note: the "possible solutions" suggested above do nothing for me.While I was browsing through the issues on Sharp's repository, I came across this issue where someone hinted at the possibility of NPM lockfile bug.
Solution
I simply regenerate package-lock.json file by running
npm install
, and now I can see that thesharp/build/Release
directory has been created.Problem
During a chat with the local model, I was getting no response. Instead, I got this error:
Solution
Installing
encoding
would solve this problem, but this issue has already been resolved in a later version of supabase-js. So I just upgraded that library to the latest version.