Tasker Rocket 🚀

The repository for Tasker Rocket 🚀, aka the new Tasker application. This project aims to be a smart front-end for the Tasker-Rocket-content repository. The content repository is responsible for providing the content.

Installation

The installation is quite simple, just prepare the .env file, run npm install and npm run dev and you are good to go.

First, copy the .env.example to .env and fill in the required values.

Please note that the content repository needs to have an accessible main branch. Otherwise, the app will not be able to load the sidebar.

cp .env.example .env

Now you need to retrieve the Supabase URL, this should be provided to you by your organisation. For Windesheim students it can be found here

Then install the dependencies of our project:

npm install

After installing the packages you can now run the app:

npm run dev

Open http://localhost:3000 with your browser to see the result.

Updates

It's important to keep our dependencies up to date, so packages should be updated regularly using the instructions below.

Minor-updates

Minor-updates can be performed by using the command of below:

npm update

Major-updates

Performing major-updates is a bit trickier, first identify the outdated dependencies.

npm outdated

Then update each package one-by-one by reinstalling it

npm install <packagename>@latest

Upgrade all packages at once

It can be quite cumbersome to upgrade each package manually, the npm-check-updates-package can do this for us.

Usage

Show all new dependencies (excluding peerDependencies) for the project in the current directory:

$ npx npm-check-updates --peer
Checking package.json
[====================] 5/5 100%

 eslint             7.32.0  →    8.0.0
 prettier           ^2.7.1  →   ^3.0.0
 svelte            ^3.48.0  →  ^3.51.0
 typescript         >3.0.0  →   >4.0.0
 untildify          <4.0.0  →   ^4.0.0
 webpack               4.x  →      5.x

Run npx npm-check-updates --peer -u to upgrade package.json

Upgrade a project's package file:

Make sure your package file is in version control and all changes have been committed. This will overwrite your package file.

$ npx npm-check-updates --peer -u
Upgrading package.json
[====================] 1/1 100%

 express           4.12.x  →   4.13.x

Run npm install to install new versions.