@nestjs/common - npm Package Compare versions

Comparing version 11.1.19 to 11.1.20

decorators/core/use-pipes.decorator.js

@@ -33,2 +33,3 @@ "use strict";
         if (descriptor) {
+            (0, validate_each_util_1.validateEach)(target.constructor, pipes, isPipeValid, '@UsePipes', 'pipe');
             (0, extend_metadata_util_1.extendArrayMetadata)(constants_1.PIPES_METADATA, pipes, descriptor.value);
@@ -35,0 +36,0 @@ return descriptor;

package.json

 {
   "name": "@nestjs/common",
-  "version": "11.1.19",
+  "version": "11.1.20",
   "description": "Nest - modern, fast, powerful node.js web framework (@common)",
@@ -41,3 +41,3 @@ "author": "Kamil Mysliwiec",
   },
-  "gitHead": "67309956821c0626c050fe6725c90645d2577e3d"
+  "gitHead": "7caeb3fb70de81085c4c3e8502a2a0e62e4f8eda"
 }

pipes/file/file-type.validator.js

@@ -26,2 +26,14 @@ "use strict";
         }
+        /**
+         * If the file buffer is not available, and fallbackToMimetype is not enabled,
+         * we cannot perform magic number validation,
+         * so we return a specific error message indicating
+         * that validation could not be performed due to missing buffer.
+         */
+        if (file?.mimetype &&
+            !file.buffer &&
+            !this.validationOptions?.fallbackToMimetype &&
+            !this.validationOptions?.skipMagicNumbersValidation) {
+            return `Validation failed (file buffer is not available; file type validation could not be performed; expected type is ${this.validationOptions.fileType})`;
+        }
         if (file?.mimetype) {
@@ -28,0 +40,0 @@ const baseMessage = `Validation failed (current file type is ${file.mimetype}, expected type is ${this.validationOptions.fileType})`;

pipes/parse-date.pipe.js

@@ -28,3 +28,3 @@ "use strict";
         }
-        if (!value) {
+        if ((0, shared_utils_1.isNil)(value) || value === '') {
             throw this.exceptionFactory('Validation failed (no Date provided)');
@@ -31,0 +31,0 @@ }

Readme.md

@@ -32,3 +32,3 @@ <p align="center">
 
-<p>In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like <a href="https://angular.io/" target="_blank">Angular</a>, <a href="https://github.com/facebook/react" target="_blank">React</a>, and <a href="https://github.com/vuejs/vue" target="_blank">Vue</a>, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.</p>
+<p>In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like <a href="https://angular.dev/" target="_blank">Angular</a>, <a href="https://react.dev/" target="_blank">React</a>, and <a href="https://vuejs.org/" target="_blank">Vue</a>, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.</p>
 <p>Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.</p>
@@ -99,2 +99,3 @@
 <td align="center" valign="middle"><a href="https://pandektes.com" target="_blank"><img src="https://nestjs.com/img/logos/pandektes-logo.png" width="65" valign="middle" /></a></td>
+<td align="center" valign="middle"><a href="https://www.fintechcrafts.com/" target="_blank"><img src="https://nestjs.com/img/logos/fintechcrafts-logo.svg" width="65" valign="middle" /></a></td>
 </tr>
@@ -101,0 +102,0 @@ </table>

New alerts

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 2 instances in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

Fixed alerts

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 2 instances in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

464316

0.21%

Lines of code

10870

0.12%

Number of lines in readme file

148

0.68%

No dependency changes