Closed brentonv closed 2 months ago
Hi @brentonv, thanks for reporting this. I think this is happening because the scripts
in package.json
are written for *NIX systems like Linux and macOS. Are you able to use WSL for development for this project? That should resolve the issues you're seeing.
I think this is happening because the
scripts
inpackage.json
are written for *NIX systems like Linux and macOS
Yeah I get this with npm install
:
npm ERR! Error: No native build was found for platform=win32 arch=x64 runtime=node abi=115 uv=1 libc=glibc node=20.12.1
npm ERR! attempted loading from: C:\Users\Brenton\Downloads\chitchatter-develop\node_modules\lmdb and package: @lmdb/lmdb-win32-x64
Thanks to everyone involved, this project is brilliant
Yeah I get this with
npm install
: npm ERR! Error: No native build was found for platform=win32 arch=x64 runtime=node abi=115 uv=1 libc=glibc node=20.12.1 npm ERR! attempted loading from: C:\Users\Brenton\Downloads\chitchatter-develop\node_modules\lmdb and package: @lmdb/lmdb-win32-x64
Thanks for sharing this! It's not surprising that various things aren't working properly in Windows, as I primarily develop on Linux systems.
I'll add a note in the README to use WSL when developing on Windows.
Thanks to everyone involved, this project is brilliant
Thank you! 🙂
NodeJS and NPM are current
package.json
"build:app": "cross-env VITE_HOMEPAGE=$(npm pkg get homepage) vite build" fails "build:sdk": "parcel build sdk/sdk.ts --no-content-hash" worksnpm run dev
npm run test
npm run build