@sentry/profiling-node 8.36.0 → 8.37.1

package/README.md

@@ -305,7 +305,7 @@ In that case it is possible that the function name may end up being reported to
 
 No. All instances of the profiler are scoped per thread In practice, this means that starting a transaction on thread A
 and delegating work to thread B will only result in sample stacks being collected from thread A. That said, nothing
-should prevent you from starting a transaction on thread B concurrently which will result in two independant profiles
+should prevent you from starting a transaction on thread B concurrently which will result in two independent profiles
 being sent to the Sentry backend. We currently do not do any correlation between such transactions, but we would be open
 to exploring the possibilities. Please file an issue if you have suggestions or specific use-cases in mind.
 

package/bindings/cpu_profiler.cc

@@ -351,7 +351,7 @@ v8::CpuProfile *SentryProfile::Stop(Profiler *profiler) {
                               v8::NewStringType::kNormal)
           .ToLocalChecked());
 
-  // Remove the meemory sampler
+  // Remove the memory sampler
   profiler->measurements_ticker.remove_heap_listener(id, memory_sampler_cb);
   profiler->measurements_ticker.remove_cpu_listener(id, cpu_sampler_cb);
   // If for some reason stopProfiling was called with an invalid profile title

package/lib/cjs/index.js

@@ -50,7 +50,7 @@ function importCppBindingsModule() {
     return require(`${binaryPath}.node`);
   }
 
-  // We need the fallthrough so that in the end, we can fallback to the require dynamice require.
+  // We need the fallthrough so that in the end, we can fallback to the dynamic require.
   // This is for cases where precompiled binaries were not provided, but may have been compiled from source.
   if (platform === 'darwin') {
     if (arch === 'x64') {
@@ -531,7 +531,7 @@ function findProfiledTransactionsFromEnvelope(envelope) {
       const event = item[j];
 
       if (!event) {
-        // Shouldnt happen, but lets be safe
+        // Shouldn't happen, but lets be safe
         continue;
       }
 

package/lib/esm/index.js

@@ -58,7 +58,7 @@ function importCppBindingsModule() {
     return require(`${binaryPath}.node`);
   }
 
-  // We need the fallthrough so that in the end, we can fallback to the require dynamice require.
+  // We need the fallthrough so that in the end, we can fallback to the dynamic require.
   // This is for cases where precompiled binaries were not provided, but may have been compiled from source.
   if (platform === 'darwin') {
     if (arch === 'x64') {
@@ -539,7 +539,7 @@ function findProfiledTransactionsFromEnvelope(envelope) {
       const event = item[j];
 
       if (!event) {
-        // Shouldnt happen, but lets be safe
+        // Shouldn't happen, but lets be safe
         continue;
       }
 

package/lib/esm/package.json

@@ -1 +1 @@
-{"type":"module","version":"8.36.0","sideEffects":false}
+{"type":"module","version":"8.37.1","sideEffects":false}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/profiling-node",
-  "version": "8.36.0",
+  "version": "8.37.1",
   "description": "Official Sentry SDK for Node.js Profiling",
   "repository": "git://github.com/getsentry/sentry-javascript.git",
   "homepage": "https://github.com/getsentry/sentry-javascript/tree/master/packages/profiling-node",
@@ -75,10 +75,10 @@
     "test": "cross-env SENTRY_PROFILER_BINARY_DIR=lib jest --config jest.config.js"
   },
   "dependencies": {
-    "@sentry/core": "8.36.0",
-    "@sentry/node": "8.36.0",
-    "@sentry/types": "8.36.0",
-    "@sentry/utils": "8.36.0",
+    "@sentry/core": "8.37.1",
+    "@sentry/node": "8.37.1",
+    "@sentry/types": "8.37.1",
+    "@sentry/utils": "8.37.1",
     "detect-libc": "^2.0.2",
     "node-abi": "^3.61.0"
   },

package/scripts/check-build.js

@@ -1,4 +1,4 @@
-// This is a build scripts, so some logging is desireable as it allows
+// This is a build script, so some logging is desirable as it allows
 // us to follow the code path that triggered the error.
 /* eslint-disable no-console */
 const fs = require('fs');

package/scripts/copy-target.js

@@ -1,4 +1,4 @@
-// This is a build scripts, so some logging is desireable as it allows
+// This is a build script, so some logging is desirable as it allows
 // us to follow the code path that triggered the error.
 /* eslint-disable no-console */
 const fs = require('fs');

package/scripts/prune-profiler-binaries.js

@@ -1,6 +1,6 @@
 #! /usr/bin/env node
 
-// This is a build scripts, so some logging is desireable as it allows
+// This is a build script, so some logging is desirable as it allows
 // us to follow the code path that triggered the error.
 /* eslint-disable no-console */
 const fs = require('fs');
@@ -88,7 +88,7 @@ if (!SOURCE_DIR) {
 
 if (!PLATFORM && !ARCH && !STDLIB) {
   ARGV_ERRORS.push(
-    `❌ Sentry: Missing argument values, pruning requires either --target_platform, --target_arch or --targer_stdlib to be passed as argument values.\n Example: sentry-prune-profiler-binaries --target_platform=linux --target_arch=x64 --target_stdlib=glibc\n
+    `❌ Sentry: Missing argument values, pruning requires either --target_platform, --target_arch or --target_stdlib to be passed as argument values.\n Example: sentry-prune-profiler-binaries --target_platform=linux --target_arch=x64 --target_stdlib=glibc\n
 If you are unsure about the execution environment, you can opt to skip some values, but at least one value must be passed.`,
   );
 }