feat: support npm workspaces for local development

Add workspaces configuration, turbo.json for build orchestration, and
workspace-aware scripts for developing with local frontend apps and
frontend-base.

Also, since npm skips bin-linking for workspace packages during install,
do it when frontend-base is built.

Part of openedx/frontend-base#184

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: arbrandes

.gitignore

@@ -3,7 +3,9 @@ npm-debug.log
 coverage
 module.config.js
 dist/
+packages/
 /*.tgz
+/.turbo
 
 ### i18n ###
 src/i18n/transifex_input.json

Makefile

@@ -0,0 +1,23 @@
+TURBO = TURBO_TELEMETRY_DISABLED=1 turbo --dangerously-disable-package-manager-check
+
+.PHONY: bin-link build-packages clean-packages clean dev-packages
+
+# NPM doesn't bin-link workspace packages during install, so it must be done manually.
+bin-link:
+	[ -f packages/frontend-base/package.json ] && npm rebuild --ignore-scripts @openedx/frontend-base || true
+
+build-packages:
+	$(TURBO) run build
+	$(MAKE) bin-link
+
+clean-packages:
+	$(TURBO) run clean
+
+dev-packages:
+	$(TURBO) run watch:build dev:site
+
+dev-site: bin-link
+	npm run dev
+
+clean:
+	rm -rf dist

README.rst

@@ -52,6 +52,62 @@ created when copying this template above.
 The dev server is running at `http://apps.local.openedx.io:8080 <http://apps.local.openedx.io:8080>`_
 or whatever port you setup.
 
+Local Development with Workspaces
+==================================
+
+This repository supports `npm workspaces`_ to enable local development of
+frontend apps (e.g., ``frontend-app-authn``, ``frontend-app-learner-dashboard``)
+and ``frontend-base`` itself, all running together in the context of a site.
+
+The ``packages/`` directory (gitignored) holds local checkouts of packages being
+developed.  These act as development-only overrides of the npm-published
+versions.
+
+Since symlinks cause module resolution failures (Node.js resolves to the real
+path, breaking hoisted dependency resolution), local checkouts should either be
+made directly under ``packages/`` or made available via bind mounts (or volume
+mounts, if running under Docker).  For example, if the checkouts are siblings
+of this repository::
+
+  mkdir -p packages/{frontend-base,frontend-app-authn,frontend-app-learner-dashboard}
+  cd packages
+  for i in *; do sudo mount --bind ../../${i} ${i}; done
+  cd ..
+  npm install
+
+`bindfs`_ can be used instead of ``sudo mount --bind`` to avoid requiring root
+privileges.
+
+.. _bindfs: https://bindfs.org/
+.. _npm workspaces: https://docs.npmjs.com/cli/using-npm/workspaces
+
+Why Turborepo
+-------------
+
+Workspace packages must be built in dependency order — for example,
+``frontend-base`` before apps that depend on it — but npm is not smart enough
+to do this on its own.  `Turborepo`_ handles this automatically via
+``dependsOn: ["^build"]`` in ``turbo.json``, building the dependency graph and
+running tasks in the correct topological order.
+
+It also enables watch mode without race conditions: the ``clean`` target is
+decoupled from ``build`` so that watch rebuilds overwrite in place without
+wiping ``dist/``.
+
+Note that Turborepo collects anonymous telemetry by default. To disable it, set
+``TURBO_TELEMETRY_DISABLED=1`` in your environment.
+
+.. _Turborepo: https://turbo.build/
+
+Workspace Scripts
+-----------------
+
+- ``npm run build:packages`` — Build all workspace packages in dependency order.
+- ``npm run clean:packages`` — Run the ``clean`` script in each workspace package.
+- ``npm run dev:packages`` — Watch-build all workspace packages and start the
+  dev server, so that changes to any local dependency are picked up
+  automatically.
+
 Internationalization
 ====================