a handful of scripts to use on the command-line to do basic tools, like compile all the TS files down to a single JS file, or run lint, or (often used in collaborative, pro environments) run lint & unit tests before you’re allowed to commit ?.Let people know who created your repo, what it does, etc. a bunch of keywords like “name”, “license”, “author”, and whatnot.There’s generally three sections to the package file:.The package.json will be where we store information about that library. For example, in order to tell the IDE about Screeps objects (like Game and Memory), constants (like FIND_MY_SCREEPS and WORK), and types (like Room and Creep), we need to include a library for that.This is basically the instruction file (or config) for NPM, which (when you run ‘npm install’) will take your libraries and stuff and tell your IDE and your compiler to behave like proper citizens.
JS files from Tutorial 4 into the src folder create a folder called ‘src’ inside the repo.it’ll warn you that you just cloned an empty repo.should be something like Go back to VS Code, in the Terminal window:.you want the ssh option that was the point of all that SSH crap.If you don’t see that box, look for the Clone button, often next to the “Use this template” button (which is notably in green). GitHub should tell you the proper command-line if you go to the repo and see the light-blue “Quick setup” box, that’s the place.back in the VS PowerShell, in your Screeps folder, clone your repo.pub file from step 4, and give it a title, and Add click on your profile image (top-right).choose Notepad! or your other favorite text editor.right-click on “id_rsa.pub” and click Open With….
But if you’re gonna use this key to put real code on the internet, all someone would need to sabotage you would be (A) this file, and (B) your passphrase.
Write the password on a sticky and put that on your monitor. Someone would need access to your computer to use it anyway. It probably doesn’t need to be too secure.