Skip to content

Latest commit

 

History

History
37 lines (25 loc) · 2.05 KB

README.md

File metadata and controls

37 lines (25 loc) · 2.05 KB

LearnTrack

LearnTrack is a chrome extension that helps you stay organized by tracking your daily tasks and the time spent on each. It monitors which websites you spend time on and shows you how your time is distributed. You can also track your progress by viewing completed tasks over time in your study plan.

Learntrack was originally hosted on the chrome webstore but has since be removed due to a lack of time to work on the project. I'm leaving it on Github for the benefit of those who would like to use it or would like to continue to develop it.

Getting Started

  1. npm i to install dependancies
  2. npm start to start running the fast development mode Webpack build process that bundle files into the dist folder
  3. npm i --save-dev <package_name> to install new packages

Loading The Chrome Extension

  1. Open Chrome and navigate to chrome://extensions/
  2. Toggle on Developer mode in the top right corner
  3. Click Load unpacked
  4. Select the entire dist folder

Important Initial Steps

  1. git init to start a new git repo for tracking your changes, do an initial base commit with all the default files
  2. Update package.json, important fields include author, version, name and description
  3. Update manifest.json, important fields include version, name and description
  4. Update webpack.commmon.js, the title in the getHtmlPlugins function should be your extension name

Production Build

  1. npm run build to generate a minimized production build in the dist folder
  2. ZIP the entire dist folder (e.g. dist.zip)
  3. Publish the ZIP file on the Chrome Web Store Developer Dashboard!

Important Default Boilerplate Notes

  • Folders get flattened, static references to images from HTML do not need to be relative (i.e. icon.png instead of ../static/icon.png)
  • Importing local ts/tsx/css files should be relative, since Webpack will build a dependancy graph using these paths
  • Update the manifest file as per usual for chrome related permissions, references to files in here should also be flattened and not be relative