fix(tracking): remove tracking and codebytes

.circleci/config.yml

@@ -114,7 +114,6 @@ jobs:
       - *set_npm_token
       - *restore_yarn_cache
       - run: yarn --production=false --frozen-lockfile
-      - run: yarn run install:sibling-dependencies
       - *save_yarn_cache
       - *save_node_modules
 
@@ -141,7 +140,7 @@ jobs:
           name: Run test suite
           command: |
             export TESTFILES=$(yarn --silent test --listTests | xargs realpath -q --relative-to=$PWD "$1" | sort | circleci tests split --split-by=timings)
-            yarn test --ci --runInBand --runTestsByPath ${TESTFILES} --coverage --reporters="default" --reporters="jest-junit"
+            yarn test --ci --runInBand --runTestsByPath ${TESTFILES} --coverage --passWithNoTests --reporters="default" --reporters="jest-junit"
           environment:
             JEST_JUNIT_OUTPUT_DIR: /tmp/test-results/junit
             JEST_JUNIT_ADD_FILE_ATTRIBUTE: 'true'

README.md

@@ -37,10 +37,10 @@ Every PR that changes files in a package publishes alpha releases that you can u
 For quicker development cycles, it's possible to run a pre-published version of a client-modules package in another project.
 We do that using symlinks (the following instructions assume you have set up and built client-modules):
 
-1. `cd /path/to/client-modules/packages/tracking`
+1. `cd /path/to/client-modules/packages/eslint-config`
 1. `yarn link`
 1. `cd path/to/other/repo`
-1. `yarn link @codecademy/tracking`
+1. `yarn link @codecademy/eslint-config`
 1. `yarn install`
 
 ### Adding a New Package

package.json

@@ -24,7 +24,6 @@
     "build": "turbo run build --concurrency=3",
     "build-all": "yarn build",
     "start:storybook": "cd ./packages/styleguide && yarn start",
-    "install:sibling-dependencies": "cd ./packages/codebytes && yarn --focus",
     "start": "yarn && yarn start:storybook"
   },
   "lint-staged": {