@netlify/plugin-emails - npm Package Compare versions

Comparing version 0.0.39-preview to 0.2.1-preview

package.json

 {
   "name": "@netlify/plugin-emails",
-  "version": "0.0.39-preview",
+  "version": "0.2.1-preview",
   "description": "A build plugin that creates an email handler and processes requests to send emails",
@@ -18,8 +18,2 @@ "main": "./lib/index.js",
   },
-  "scripts": {
-    "build": "tsc --project tsconfig.build.json",
-    "watch": "tsc --project tsconfig.build.json --watch",
-    "test": "vitest -c ./src/vitest.config.ts --watch=false",
-    "coverage": "vitest run --coverage -c ./src/vitest.config.ts"
-  },
   "keywords": [
@@ -57,3 +51,9 @@ "emails",
     "vitest": "^0.25.8"
+  },
+  "scripts": {
+    "build": "tsc --project tsconfig.build.json",
+    "watch": "tsc --project tsconfig.build.json --watch",
+    "test": "vitest -c ./src/vitest.config.ts --watch=false",
+    "coverage": "vitest run --coverage -c ./src/vitest.config.ts"
   }
-}
+}

README.md

@@ -33,3 +33,3 @@ # Netlify Emails Plugin
 
-Now that the setup is complete, you can create an email directory `./emails` (default) or use a custom directory, as long as you define it in your Email Settings under ‘Template directory’.
+Now that the setup is complete, create an email directory `./emails` (default) or use a custom directory, as long as you define it in your Email Settings under ‘Template directory’.
 
@@ -36,0 +36,0 @@ Each email template should be stored under a folder name that represents the route of your template and the email file should be named `index.html`. E.g. `./emails/welcome/index.html`.

src/handler/index.ts

@@ -346,2 +346,3 @@ import { Handler } from "@netlify/functions";
             siteId = ${JSON.stringify(process.env.SITE_ID)}
+            siteName = ${JSON.stringify(process.env.SITE_NAME)}
             secret = ${JSON.stringify(process.env.NETLIFY_EMAILS_SECRET)}
@@ -348,0 +349,0 @@ url = ${JSON.stringify(process.env.URL)}

Fixed alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

61581

increased by0.09%

Lines of code

1535

increased by0.07%

Number of medium supply chain risk alerts

2

decreased by-50%

No dependency changes