payload-plugin-newsletter 0.8.5 → 0.8.6

package/CHANGELOG.md

@@ -1,3 +1,19 @@
+## [0.8.6] - 2025-07-02
+
+### Fixed
+- **Critical**: Fixed all endpoint handlers for Payload v3 compatibility
+  - ✅ Updated request body access from `req.data` to `await req.json()`
+  - ✅ Fixed cookie access from `req.cookies` to parsing from headers
+  - ✅ All endpoints now properly handle request data
+  - Affects: signin, subscribe, unsubscribe, preferences, verify-magic-link, me endpoints
+- **Resolves**: "Cannot destructure property 'email' of 'req.data' as it is undefined" error
+- **Resolves**: "Cannot read properties of undefined (reading 'newsletter-auth')" error
+
+### Technical Details
+- Updated all POST endpoints to use `const data = await req.json()` per Payload v3 patterns
+- Updated cookie parsing to read from `req.headers.get('cookie')` instead of `req.cookies`
+- All endpoint handlers now follow official Payload v3 REST API documentation patterns
+
 ## [0.8.5] - 2025-07-01
 
 ### Fixed

package/CLAUDE.md

@@ -4,6 +4,59 @@ This file contains development guidelines and reference information for Claude w
 
 **Note**: This plugin is developed by Aniket Panjwani, who uses Broadcast (sendbroadcast.net) for newsletter management.
 
+## Payload CMS Documentation Reference
+
+The official Payload CMS documentation is available locally at:
+`/Users/aniketpanjwani/Projects/reference_repos/payload/docs/`
+
+Key directories for plugin development:
+- `plugins/` - Official plugin examples and patterns
+- `rest-api/` - REST API documentation and endpoint patterns
+- `custom-components/` - Custom views and UI components
+- `configuration/` - Core configuration patterns
+- `hooks/` - Hook system documentation
+- `authentication/` - Auth patterns and examples
+- `local-api/` - Local API usage patterns
+- `typescript/` - TypeScript patterns and best practices
+
+When developing features, always reference these docs for:
+1. Current Payload v3 patterns and best practices
+2. Endpoint handler signatures and request/response formats
+3. Authentication and authorization patterns
+4. Plugin architecture guidelines
+5. TypeScript type definitions and interfaces
+
+### Critical Payload v3 Endpoint Patterns
+
+From the official Payload v3 REST API documentation (`rest-api/overview.mdx`):
+
+1. **Request Body Access**: 
+   - Data is NOT automatically appended to the request
+   - Use `await req.json()` to read the body
+   - Or use `await addDataAndFileToRequest(req)` helper to mutate req and add req.data
+
+2. **Response Format**:
+   - Return `Response.json()` objects, not `res.status().json()`
+   - Example: `return Response.json({ message: 'success' }, { status: 200 })`
+
+3. **Cookie Access**:
+   - Cookies are NOT available at `req.cookies`
+   - Access via request headers instead
+
+4. **Handler Signature**:
+   ```ts
+   handler: async (req) => {
+     // NOT (req, res) - just req!
+     const data = await req.json() // or use addDataAndFileToRequest(req)
+     return Response.json({ result: 'data' })
+   }
+   ```
+
+**Current Plugin Bug**: The newsletter plugin endpoints are using old Payload v2 patterns:
+- Trying to access `req.data` directly (undefined)
+- Trying to access `req.cookies` directly (undefined)
+- Need to update ALL endpoints to use the new patterns
+
 ## Important Security Guidelines
 
 **NEVER include any of the following in the repository:**

package/dist/index.cjs

@@ -1451,6 +1451,7 @@ var createSubscribeEndpoint = (config) => {
     method: "post",
     handler: async (req) => {
       try {
+        const data = await req.json();
         const {
           email,
           name,
@@ -1459,7 +1460,7 @@ var createSubscribeEndpoint = (config) => {
           leadMagnet,
           surveyResponses,
           metadata = {}
-        } = req.data;
+        } = data;
         const trimmedEmail = email?.trim();
         const validation = validateSubscriberData({ email: trimmedEmail, name, source });
         if (!validation.valid) {
@@ -1621,7 +1622,8 @@ var createVerifyMagicLinkEndpoint = (config) => {
     method: "post",
     handler: async (req) => {
       try {
-        const { token } = req.data;
+        const data = await req.json();
+        const { token } = data;
         if (!token) {
           return Response.json({
             success: false,
@@ -1826,7 +1828,8 @@ var createUpdatePreferencesEndpoint = (config) => {
             error: error instanceof Error ? error.message : "Invalid token"
           }, { status: 401 });
         }
-        const { name, locale, emailPreferences } = req.data;
+        const data = await req.json();
+        const { name, locale, emailPreferences } = data;
         const updateData = {};
         if (name !== void 0) {
           updateData.name = name;
@@ -1877,7 +1880,8 @@ var createUnsubscribeEndpoint = (config) => {
     method: "post",
     handler: async (req) => {
       try {
-        const { email, token } = req.data;
+        const data = await req.json();
+        const { email, token } = data;
         if (!email && !token) {
           return Response.json({
             success: false,
@@ -2024,7 +2028,8 @@ var createSigninEndpoint = (config) => {
     method: "post",
     handler: async (req) => {
       try {
-        const { email } = req.data;
+        const data = await req.json();
+        const { email } = data;
         const validation = validateSubscriberData({ email });
         if (!validation.valid) {
           return Response.json({
@@ -2105,7 +2110,14 @@ var createMeEndpoint = (config) => {
     method: "get",
     handler: async (req) => {
       try {
-        const token = req.cookies?.["newsletter-auth"];
+        const cookieHeader = req.headers.get("cookie") || "";
+        const cookies = Object.fromEntries(
+          cookieHeader.split("; ").map((c) => {
+            const [key, ...value] = c.split("=");
+            return [key, value.join("=")];
+          })
+        );
+        const token = cookies["newsletter-auth"];
         if (!token) {
           return Response.json({
             success: false,