Fix pre-push hook when no terminal is attached (#475)

* Fix pre-push hook when no terminal is attached

Pushing from non-interactive environments (Claude Code, IDE
integrations, CI) failed for two reasons:

- The hook's `exec < /dev/tty` errors out when no TTY exists. Only
  redirect stdin when /dev/tty is actually readable.
- Git feeds the pre-push hook its ref list on stdin, so without the
  redirect, copy-shared-files' confirmation prompt read a ref line as
  the answer and aborted the push. Only prompt when stdin is a
  terminal; otherwise proceed with the default.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Move pnpm settings from .npmrc to pnpm-workspace.yaml

The root .npmrc contained only pnpm-specific workspace settings, which
npm doesn't understand, so every `npm run` (including the pre-push
hook) printed "Unknown project config" warnings. pnpm 10 reads its
settings from pnpm-workspace.yaml, which npm never touches.

No resolution change: `pnpm install --lockfile-only` leaves
pnpm-lock.yaml untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: brianstrauch

.husky/pre-push

@@ -1,5 +1,9 @@
 #!/bin/bash
 set -euo pipefail
 
-exec < /dev/tty
+# Attach the terminal so copy-shared-files can prompt, but skip when there is
+# no TTY (Claude Code, IDE integrations, CI).
+if sh -c ': < /dev/tty' 2> /dev/null; then
+  exec < /dev/tty
+fi
 npm run copy-shared-files

.npmrc

@@ -146,11 +146,16 @@ if (numSharedFilesChanged === 0 && !hasNewSamples) {
 
 await $`git add ${'./.scripts/list-of-samples.json'}`;
 
-let [answer] = await question(
-  `Running pre-commit hook.
+let answer;
+// Only prompt when stdin is a terminal — in non-interactive runs (Claude Code, CI,
+// git hooks where stdin carries ref data), proceed with the default.
+if (process.stdin.isTTY) {
+  [answer] = await question(
+    `Running pre-commit hook.
 This will overwrite changes made to most config files in samples (like ${chalk.bold('hello-world/tsconfig.json')}).
 Proceed? [Y/n] `
-);
+  );
+}
 
 if ((answer ?? 'y').toUpperCase() !== 'Y') {
   console.log(`To change config files, edit them in the ${chalk.bold('.shared/')} directory.\nAborting commit.`);

.scripts/copy-shared-files.mjs

@@ -10,6 +10,22 @@ packages:
   - 'food-delivery/apps/*'
   - 'food-delivery/packages/*'
   - 'polling/*'
+
+linkWorkspacePackages: true
+sharedWorkspaceLockfile: true
+hoist: false
+
+# By default, PNPM hoists eslint and prettier to the workspace root, but that may causes issues
+# with this workspace, as some samples have completely different versions of these packages, or
+# depends on incompatible plugins.
+#
+# The monorepo sample uses postcss with an external configuration file that refers to plugins by
+# their package name, rather than passing objects. That doesn't work with PNPM's strict node_modules
+# structure. To work around this, hoist all postcss-* packages.
+# FIXME: Can't we do something equivalent at the project-level instead?
+publicHoistPattern:
+  - postcss-*
+
 allowBuilds:
   '@nestjs/core': true
   '@swc/core': true