-
Notifications
You must be signed in to change notification settings - Fork 26
Open
Description
From https://reasonml.chat/t/is-reprocessing-alive/2045/10
cc @jdeisenberg
reasonlab> rm -rf reprocessing-example
reasonlab> !?clone
git clone https://github.com/bsansouci/reprocessing-example.git
Cloning into 'reprocessing-example'...
remote: Enumerating objects: 6, done.
remote: Counting objects: 100% (6/6), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 215 (delta 2), reused 0 (delta 0), pack-reused 209
Receiving objects: 100% (215/215), 486.29 KiB | 5.40 MiB/s, done.
Resolving deltas: 100% (106/106), done.
reasonlab> cd reprocessing-example
reprocessing-example> ls
bsconfig.json index.html package.json README.md require_polyfill.js src
reprocessing-example> npm install
> [email protected] postinstall /home/david/reasonlab/reprocessing-example/node_modules/sdl2
> node postinstall.js
No pre-built binaries for linux, downloading source
Unzip successful.
Building from source, will take a minute or two.
Looks like SDL2 built successfully.
> [email protected] postinstall /home/david/reasonlab/reprocessing-example/node_modules/bsb-native
> node postinstall.js
Unzip successful.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN reprocessing-example@ No repository field.
npm WARN reprocessing-example@ No license field.
added 11 packages from 8 contributors and audited 15 packages in 50.28s
found 0 vulnerabilities
reprocessing-example> npm run build
> reprocessing-example@ build /home/david/reasonlab/reprocessing-example
> bsb -make-world
bs-platform version mismatch Running bsb 4.0.11 (/home/david/reasonlab/reprocessing-example/node_modules/bsb-native) vs vendored 6.2.1 (/home/david/.nvm/versions/node/v11.7.0/lib/node_modules/bs-platform)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! reprocessing-example@ build: `bsb -make-world`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the reprocessing-example@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/david/.npm/_logs/2019-12-04T01_41_48_361Z-debug.log
jul1u5
Metadata
Metadata
Assignees
Labels
No labels