Open tddschn opened 5 months ago
I tried to deploy sqlite databases in other projects and I found that in new projects the plugin don't work anymore, while in old projects they still work. I don't know why, I haven't reach any usage limit on Vercel. I think one possible explanation is that my new projects are somehow marked to use a new build env on Vercel, but there's no way for me to know for sure.
All my new projects failed like this:
datasette publish vercel --project rick-n-morty-datasette-vercel data/rnm.db --install datasette-search-all --install datasette-render-timestamps --install datasette-render-images --install datasette-uptime --install datasette-render-html \
--install datasette-pretty-json --metadata data/metadata.yml
(node:48325) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Vercel CLI 33.6.1
WARN! `--confirm` is deprecated, please use `--yes` instead
❗️ The `name` property in vercel.json is deprecated (https://vercel.link/name-prop)
🔗 Linked to tddschn/rick-n-morty-datasette-vercel (created .vercel and added it to .gitignore)
🔍 Inspect: https://vercel.com/tddschn/<proj>/MUoFFHYUaqGqNVkEF7PYTntQ5eBY [4s]
✅ Production: https://rick-n-morty-datasette-vercel-h7l7l8hry-tddschn.vercel.app [4s]
Error: spawn pip3.9 ENOENT
Error: Command '['vercel', '--confirm', '--prod', '--env', 'DATASETTE_SECRET=<sec>']' returned non-zero exit status 1.
Failed to run "pip3.9 install --disable-pip-version-check --target . werkzeug==1.0.1"
is in the deployment log on Vercel dashboard. I find it extremely weird since any of the dependencies listed in requirements.txt
in the generated dir doesn't reply on werkzeug either directly or indirectly, and the deployment log doesn't show more information.
@simonw Could you take a look at this issue please?
I had the same problem. It seems like changing the Node.js version from the Project Settings (under General) to 18.x solves it.
Confirming that changing Node.js to 18.x solved the problem.
I experienced the same issue and before reading this found a different solution, which was to change the vercel.json output in the plugin options to
"use": "@vercel/python@4.3.1"
(the default setting is current "use": "@vercel/python@3.0.7"
). It doesn't seem like a great idea to supply my own vercel.json file because then any other vercel.json updates are not propogated but it works.
I chose 4.3.1 because it seemed to be the most popular option here: https://www.npmjs.com/package/@vercel/python?activeTab=versions
This would be a simple change to the _init_.py
file... but not sure if it would break the solutions above?
Node version on Vercel remains 20.x
datasette, version 1.0a12
datasette-publish-vercel: latest version
Vercel CLI 33.6.1 (can successfully deploy any other python serverless projects, just doesn't work with datasette-publish-vercel)