From 3dd8a9f758e267f80d812a68b46f555ff7feed3d Mon Sep 17 00:00:00 2001 From: Geremia Taglialatela Date: Sun, 13 Oct 2024 11:09:09 +0200 Subject: [PATCH] Fix package.json engines and required Node version Including "pnpm" in the engines field of your package.json for a library is generally not recommended, even if you use it for building the library. The engines field is typically used to specify runtime environments (such as Node.js versions) that are required to run the library, not the tools used to build or develop it. Most developers expect the engines field to list only the runtime requirements, not development tools like package managers. --- package.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/package.json b/package.json index 02081743..ee2a33ae 100644 --- a/package.json +++ b/package.json @@ -38,8 +38,7 @@ "main": "dist/client-side-validations.js", "module": "dist/client-side-validations.esm.js", "engines": { - "node": ">= 18.0", - "pnpm": "^9.12.1" + "node": ">= 18.12" }, "packageManager": "pnpm@^9.12.1", "browserslist": [