Skip to content
GabenGarPublic

About

Resources

Stars

0 stars

Watchers

1 watching

Forks

Latest commit

 

History

168 Commits

Folders and files

Repository files navigation

TODOs

Table of Contents

Requrements

NodeJS - 20.9+

Link Overwatch Extension

  1. Clone the repo:
    git clone https://github.com/GabenGar/todos.git
  2. Switch to the repo:
    cd ./todos
  3. Create a pruned output for the extension package:
    npx turbo prune "link-overwatch" --out-dir "./dist"
  4. Switch into it
    cd dist
  5. Install dependencies:
    npm install
  6. Build extension:
    npm run build
  7. The extension archive will be located in /apps/extension/dist.

Installation

  1. Clone the repo:

    git clone https://github.com/GabenGar/todos.git
  2. Switch to the repo:

    cd ./todos
  3. Install all dependencies:

    npm install
  4. Build the project:

    npm run build
  5. Start the server:

    npm run start

Develop

npm run dev

Prep the Workflow

  1. Open git config:
    open ./.git/config
  2. Add user section:
    [user]
        name = <username>
        email = <email>
  3. Add ssh key to core section:
      sshCommand = ssh -i <ssh_key_path> -F /dev/null
  4. Change push remote to ssh endpoint:
    git remote set-url --push origin git@github.com:<username>/todos.git

Turborepo

Turborepo claims that the invocation from global install will invoke local install if applicable, so it can be installed globally:

npm install turbo --global

And then instead of npm run ... commands it can be used as turbo run ....

Create a Package

turbo generate workspace --type=package --name=<name> --empty --destination=<path>
npm install

Troubleshooting

  • I get npm ERR! code ENOWORKSPACES frontend:dev: npm ERR! This command does not support workspaces. error when starting development. Run cd apps/frontend && npx next telemetry disable.

Update dependencies

The repo has a bunch of singleteon packages or the packages which don't work well when there are different versions of them across worspaces. These packages have to be pinned up to minor versions across all workspaces which depend on them and updated to the same versions at the same time.

The packages in question:

  • turbo Run npx @turbo/codemod migrate after updating to new version.

  • biome Run npx biome migrate --write after updating to new version.

  • typescript

  • @types/node Must match engines field.

  • i18next

  • i18next-resources-to-backend

  • react-i18next i18next stuff.

  • react

  • react-dom

  • @types/react

  • @types/react-dom ReactJS stuff.

  • @next/env

  • next NextJS stuff.

  • @tanstack/react-router

  • @tanstack/react-start TankStack stuff.

  • react-router

  • @react-router/express

  • @react-router/node

  • @react-router/serve

  • @react-router/dev React Router stuff.

Always run npm update after all version manipualtions are complete, and npm install afterwards, because reasons.

About

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages