Updating to the latest version
Unzip the zip file.
Make a backup copy of your prototype folder.
In your prototype, delete everything except the
You may not be able to see the
.gitfolder because files and folders that start with
.are hidden by default.
Copy all the folders from the unzipped folder to your prototype, except the
app/config.jsfile in your prototype with the
app/config.jsfile from the unzipped folder.
Compare your new
config.jsfile to the
config.jsfile in the backup you made in step 3, and copy over anything you need to from the backup - for example your service name.
app/assets/sass/patternsfrom the unzipped folder to your prototype.
app/assets/sass/componentsfrom the unzipped folder to your prototype.
app/assets/sass/application.scssfile in the unzipped folder.
Copy everything down to
// Add extra styles here, then paste it into the
app/assets/sass/application.scssfile in your prototype so it replaces everything above
// Add extra styles here.
Save the updated
app/assets/sass/application.scssfile in your prototype.
Check the latest Prototype Kit release note and follow any guidance on updating your prototype.
If your prototype has not been updated for a long time, you should also follow any guidance in release notes between the version you're updating from and the latest version. You can find out the version you're updating from in the
VERSION.txtfile in your backup folder.
In your terminal,
cdto your prototype folder.
This may take up to a minute. You can ignore any lines in the log that start with
If your prototype does not work, compare the new
package.json file to the
package.json file in the backup you made in step 3. Run
npm install PACKAGE-NAME for each package that's missing in the new file.
- raise an issue in the Prototype Kit GitHub repo
- get in touch using the #prototype-kit channel on cross-government Slack
Tell us as much as you can about the issue you're having, and the computer and operating system you're using.