@leverege/build-tools 2.113.0-quinn.1 → 2.113.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leverege/build-tools",
-  "version": "2.113.0-quinn.1",
+  "version": "2.113.0",
   "description": "A collection of build / support tools for Leverege developers",
   "main": "index.js",
   "repository": {

package/src/yarn-build.mjs

@@ -32,11 +32,18 @@ log( `Building ${packageJson.name}...` )
 
 const packageName = packageJson.name
 const mainEntry = path.join( process.env.INIT_CWD, packageJson.main )
-const root = findYarnWorkspaceRoot( process.env.INIT_CWD ) || process.env.INIT_CWD
 
-// Entry path relative to the workspace root. turbo prune preserves the
-// workspace's directory layout, so this same relative path resolves inside
-// the pruned output.
+// A null workspace root means this is a standalone (non-monorepo) package:
+// there are no sibling workspaces to prune away, so turbo prune doesn't apply
+// (it requires a workspace root and errors otherwise). In that case the
+// package itself is the whole deployable.
+const workspaceRoot = findYarnWorkspaceRoot( process.env.INIT_CWD )
+const isMonorepo = workspaceRoot != null
+const root = workspaceRoot || process.env.INIT_CWD
+
+// Entry path relative to the deployable's root. For a monorepo turbo prune
+// preserves the workspace layout under that root; for a standalone package the
+// root is the package dir itself. Either way this resolves from the buildDir.
 const main = path.relative( root, mainEntry )
 
 // Same out-of-tree staging dir the old yarn-build used. docker-to-registry
@@ -51,15 +58,28 @@ log( 'Cleaning previous build output...' )
 await $$`rm -rf ${buildDir}`.catch( () => {} )
 await $$`mkdir -p ${buildDir}`.catch( () => {} )
 
-// Prune the monorepo down to the target package and only the workspaces it
-// actually depends on (per package.json), emitting a pruned lockfile. No
-// bundling / compilation: the servers run raw ESM source, so the pruned tree
-// IS the deployable. node_modules is intentionally not copied; the Docker
-// build installs from the pruned lockfile. Without --docker, turbo emits a
-// flat pruned workspace tree (root package.json, workspace dirs, lockfile)
-// directly into the out dir.
-log( `Pruning workspace ${packageName}...` )
-await $$`yarn dlx turbo@^2 prune ${packageName} --out-dir ${buildDir}`
+if ( isMonorepo ) {
+  // Prune the monorepo down to the target package and only the workspaces it
+  // actually depends on (per package.json), emitting a pruned lockfile. No
+  // bundling / compilation: the servers run raw ESM source, so the pruned tree
+  // IS the deployable. node_modules is intentionally not copied; the Docker
+  // build installs from the pruned lockfile. Without --docker, turbo emits a
+  // flat pruned workspace tree (root package.json, workspace dirs, lockfile)
+  // directly into the out dir.
+  log( `Pruning workspace ${packageName}...` )
+  await $$`yarn dlx turbo@^2 prune ${packageName} --out-dir ${buildDir}`
+} else {
+  // Standalone package: nothing to prune. Copy the package's tracked and
+  // non-ignored files into buildDir. `git ls-files --cached --others
+  // --exclude-standard` honors .gitignore, so node_modules and build cruft are
+  // excluded while the lockfile and package.json (both tracked) come along.
+  log( 'Standalone package (no workspace root); copying source, turbo prune skipped...' )
+  const listed = await $`git -C ${process.env.INIT_CWD} ls-files --cached --others --exclude-standard`
+  const files = listed.stdout.split( '\n' ).filter( Boolean )
+  await Promise.all( files.map( rel => (
+    fs.copy( path.join( process.env.INIT_CWD, rel ), path.join( buildDir, rel ) )
+  ) ) )
+}
 
 log( 'Writing entrypoint...' )
 const entrypointFile = generateEntrypointFile( main )