@typeberry/jam 0.1.1-127cc86 → 0.1.1-4a6ffa9

package/jam-network/index.js

@@ -25425,6 +25425,34 @@ class WithDebug {
     }
 }
 
+;// CONCATENATED MODULE: ./packages/core/utils/dev.ts
+const dev_env = typeof process === "undefined" ? {} : process.env;
+/**
+ * The function will produce relative path resolver that is adjusted
+ * for package location within the workspace.
+ *
+ * Example:
+ * $ npm start -w @typeberry/jam
+ *
+ * The above command will run `./bin/jam/index.js`, however we would
+ * still want relative paths to be resolved according to top-level workspace
+ * directory.
+ *
+ * So the caller, passes the absolute workspace path as argument and get's
+ * a function that can properly resolve relative paths.
+ *
+ * NOTE: the translation happens only for development build! When
+ * we build a single library from our project, we no longer mangle the paths.
+ */
+const workspacePathFix = dev_env.NODE_ENV === "development"
+    ? (workspacePath) => (p) => {
+        if (p.startsWith("/")) {
+            return p;
+        }
+        return `${workspacePath}/${p}`;
+    }
+    : () => (p) => p;
+
 ;// CONCATENATED MODULE: ./packages/core/utils/opaque.ts
 /**
  * @fileoverview `Opaque<Type, Token>` constructs a unique type which is a subset of Type with a
@@ -25768,6 +25796,7 @@ function isResult(x) {
 
 
 
+
 ;// CONCATENATED MODULE: ./packages/core/bytes/bitvec.ts
 
 /**