Newbie question: error deploying Flowershow to Vercel using Obsidian plugin step-by-step instructions

[dldsantos]

Hello friends. Flowershow enthusiast (but newbie) here, needing help.

I'm following the tutorial steps that are included in the Obsidian plugin. trying to make Obsidian, Flowershow and Vercel work together. I've tried to quickclone and deploy to Vercel using the blue button a couple of times, but couldn't get past the Building step. Some error messages show up and, as I'm not an expert, I'm not being able to get past them.

Based on my deployment log below, could you please give me some instructions on how to get past the errors and finally have my site published from Obsidian? I love the idea and the simplicity behind Flowershow, so any help is greatly appreciated. Thanks in advance.

[08:57:15.184] Running build in Washington, D.C., USA (East) – iad1 (Hive)
[08:57:16.160] Cloning github.com/dldsantos/flowershow (Branch: main, Commit: 4249e03)
[08:57:16.505] Previous build cache not available
[08:57:16.721] Cloning completed: 559.826ms
[08:57:16.994] Running "vercel build"
[08:57:17.473] Vercel CLI 32.4.1
[08:57:18.444] Running "install" command: `npm install`...
[08:57:19.704] npm WARN ERESOLVE overriding peer dependency
[08:57:19.705] npm WARN While resolving: react-virtual@2.10.4
[08:57:19.705] npm WARN Found: react@18.2.0
[08:57:19.705] npm WARN node_modules/react
[08:57:19.706] npm WARN   react@"^18.2.0" from the root project
[08:57:19.706] npm WARN   22 more (@docsearch/react, @floating-ui/react-dom, ...)
[08:57:19.706] npm WARN 
[08:57:19.706] npm WARN Could not resolve dependency:
[08:57:19.706] npm WARN peer react@"^16.6.3 || ^17.0.0" from react-virtual@2.10.4
[08:57:19.706] npm WARN node_modules/kbar/node_modules/react-virtual
[08:57:19.706] npm WARN   react-virtual@"^2.8.2" from kbar@0.1.0-beta.40
[08:57:19.706] npm WARN   node_modules/kbar
[08:57:19.706] npm WARN 
[08:57:19.706] npm WARN Conflicting peer dependency: react@17.0.2
[08:57:19.706] npm WARN node_modules/react
[08:57:19.706] npm WARN   peer react@"^16.6.3 || ^17.0.0" from react-virtual@2.10.4
[08:57:19.707] npm WARN   node_modules/kbar/node_modules/react-virtual
[08:57:19.707] npm WARN     react-virtual@"^2.8.2" from kbar@0.1.0-beta.40
[08:57:19.707] npm WARN     node_modules/kbar
[08:57:21.193] npm WARN tarball tarball data for @portaljs/core@file:/vercel/portaljs/packages/core/portaljs-core-1.0.7.tgz (sha512-6JpIi7mt30vwLcdG3Tvy8GrAqFouVfyWvSNGu0wkMXylCZNGG1DlUiFlNSDVfrm4kXPNi4Jg807NUKhO81sarg==) seems to be corrupted. Trying again.
[08:57:21.263] npm WARN tarball tarball data for @portaljs/core@file:/vercel/portaljs/packages/core/portaljs-core-1.0.7.tgz (sha512-6JpIi7mt30vwLcdG3Tvy8GrAqFouVfyWvSNGu0wkMXylCZNGG1DlUiFlNSDVfrm4kXPNi4Jg807NUKhO81sarg==) seems to be corrupted. Trying again.
[08:57:25.614] npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
[08:57:25.911] npm WARN deprecated @silvenon/remark-smartypants@2.0.0: renamed to just "remark-smartypants"
[08:57:26.179] npm WARN deprecated puppeteer@18.2.1: < 19.4.0 is no longer supported
[08:57:27.418] npm WARN deprecated @floating-ui/react-dom-interactions@0.13.3: Package renamed to @floating-ui/react
[08:57:46.836] npm ERR! code ENOENT
[08:57:46.837] npm ERR! syscall open
[08:57:46.837] npm ERR! path /vercel/portaljs/packages/core/portaljs-core-1.0.7.tgz
[08:57:46.837] npm ERR! errno -2
[08:57:46.837] npm ERR! enoent ENOENT: no such file or directory, open '/vercel/portaljs/packages/core/portaljs-core-1.0.7.tgz'
[08:57:46.838] npm ERR! enoent This is related to npm not being able to find a file.
[08:57:46.838] npm ERR! enoent 
[08:57:46.839] 
[08:57:46.839] npm ERR! A complete log of this run can be found in: /vercel/.npm/_logs/2023-10-07T11_57_18_792Z-debug-0.log
[08:57:46.871] Error: Command "npm install" exited with 254

[rufuspollock]

Thanks for requesting help - the error seems kind of weird here. I assume you are running this build on vercel. it may be worth retrying and seeing what happens as maybe there is something up in npm.

[rufuspollock]

@dldsantos did you get this resolved?