btw explorer . opens pwd in windows explorer in git bash, pretty cool
Cloning
Use --depth to make cloning/fetching faster?
# Preserve links
npm install -g npm-safe-install
git clone https://github.com/SheepTester/scratch-gui.git
cd scratch-gui
git remote add upstream https://github.com/LLK/scratch-gui.git
Update
Run git fetch upstream develop then git merge upstream/develop when in the proper branch (16-9 or vanilla-vm-min).
If package-lock.json gets annoying and causes a phatte merge conflict, do git checkout --theirs package-lock.json (seems like you'll also have to do git add package-lock.json afterwards)
Then do nsi from npm-safe-install, not npm install because it breaks links.
Start
In each of the other repos,
- run
npm run watch if you intend to modify them, or
- run
npm run build once if you don't intend on editing the repo
If it fails because of something to do with schema-utils, run nsi once more and try again.
Then, run npm start in gui; http://localhost:8601/
Publish
NODE_ENV=production npm run build
npm run deploy
-a is important to not overwrite /16-9/ (see 5053304); this is what -a does (no longer needed because #31)
(npm run deploy -- -e branch-name will publish to /branch-name/)
vm.min.js
Used by the HTMLifier, available at https://sheeptester.github.io/scratch-vm/vm.min.js
E羊icques
# in scratch-vm
git checkout 16-9
nsi
NODE_ENV=production npm run build
npm run deploy -- -e 16-9
Vanilla
# in scratch-vm
git checkout vanilla-vm-min
nsi
NODE_ENV=production npm run build
npm run deploy -- -a
btw
explorer .opens pwd in windows explorer in git bash, pretty coolCloning
Use
--depthto make cloning/fetching faster?Update
Run
git fetch upstream developthengit merge upstream/developwhen in the proper branch (16-9orvanilla-vm-min).If
package-lock.jsongets annoying and causes a phatte merge conflict, dogit checkout --theirs package-lock.json(seems like you'll also have to dogit add package-lock.jsonafterwards)Then do
nsifrom npm-safe-install, notnpm installbecause it breaks links.Start
In each of the other repos,
npm run watchif you intend to modify them, ornpm run buildonce if you don't intend on editing the repoIf it fails because of something to do with
schema-utils, runnsionce more and try again.Then, run
npm startin gui; http://localhost:8601/Publish
(no longer needed because #31)-ais important to not overwrite/16-9/(see 5053304); this is what-adoes(
npm run deploy -- -e branch-namewill publish to/branch-name/)vm.min.jsUsed by the HTMLifier, available at https://sheeptester.github.io/scratch-vm/vm.min.js
E羊icques
Vanilla