@pnpm/core-loggers 1100.2.5 → 1100.3.0

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # @pnpm/core-loggers
 
+## 1100.3.0
+
+### Minor Changes
+
+- Restored the store block a first install prints, naming how packages were materialized and where the stores live [#13315](https://github.com/pnpm/pnpm/issues/13315):
+
+  ```text
+  Packages are hard linked from the content-addressable store to the virtual store.
+    Content-addressable store is at: ~/.local/share/pnpm/store/v11
+    Virtual store is at:             node_modules/.pnpm
+  ```
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/types@1101.7.0
+
 ## 1100.2.5
 
 ### Patch Changes

package/lib/all.d.ts

@@ -16,6 +16,7 @@ export * from './progressLogger.js';
 export * from './promptLogger.js';
 export * from './registryLogger.js';
 export * from './removalLogger.js';
+export * from './reportPackageImported.js';
 export * from './requestRetryLogger.js';
 export * from './rootLogger.js';
 export * from './scopeLogger.js';

package/lib/all.js

@@ -16,6 +16,7 @@ export * from './progressLogger.js';
 export * from './promptLogger.js';
 export * from './registryLogger.js';
 export * from './removalLogger.js';
+export * from './reportPackageImported.js';
 export * from './requestRetryLogger.js';
 export * from './rootLogger.js';
 export * from './scopeLogger.js';

package/lib/reportPackageImported.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Report one package materialized from the content-addressable store into
+ * the virtual store.
+ *
+ * The import itself runs in a `@pnpm/worker` thread, whose loggers are not
+ * connected to the reporter, so both channels are emitted here — in the main
+ * process — from the method the worker reported back. `pnpm:progress` drives
+ * the "imported" counter; `pnpm:package-import-method` tells the reporter
+ * which wording to use for the store block it prints on a first install.
+ */
+export declare function reportPackageImported(opts: {
+    method: string;
+    requester: string;
+    to: string;
+}): void;

package/lib/reportPackageImported.js

@@ -0,0 +1,27 @@
+import { packageImportMethodLogger } from './packageImportMethodLogger.js';
+import { progressLogger } from './progressLogger.js';
+/**
+ * Report one package materialized from the content-addressable store into
+ * the virtual store.
+ *
+ * The import itself runs in a `@pnpm/worker` thread, whose loggers are not
+ * connected to the reporter, so both channels are emitted here — in the main
+ * process — from the method the worker reported back. `pnpm:progress` drives
+ * the "imported" counter; `pnpm:package-import-method` tells the reporter
+ * which wording to use for the store block it prints on a first install.
+ */
+export function reportPackageImported(opts) {
+    progressLogger.debug({
+        method: opts.method,
+        requester: opts.requester,
+        status: 'imported',
+        to: opts.to,
+    });
+    if (isKnownImportMethod(opts.method)) {
+        packageImportMethodLogger.debug({ method: opts.method });
+    }
+}
+function isKnownImportMethod(method) {
+    return method === 'clone' || method === 'hardlink' || method === 'copy';
+}
+//# sourceMappingURL=reportPackageImported.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnpm/core-loggers",
-  "version": "1100.2.5",
+  "version": "1100.3.0",
   "description": "Core loggers of pnpm",
   "keywords": [
     "pnpm",
@@ -30,13 +30,13 @@
     "test": "test"
   },
   "dependencies": {
-    "@pnpm/types": "1101.6.0"
+    "@pnpm/types": "1101.7.0"
   },
   "peerDependencies": {
     "@pnpm/logger": "^1100.0.0"
   },
   "devDependencies": {
-    "@pnpm/core-loggers": "1100.2.5",
+    "@pnpm/core-loggers": "1100.3.0",
     "@pnpm/logger": "1100.0.0"
   },
   "engines": {