@kgalexander/mcreate 0.0.2

package/README.md

@@ -0,0 +1,40 @@
+# mcreate
+
+mcreate package
+
+## Local Development with npm link
+
+When using `npm link` to develop these packages locally with a Next.js application, you need to configure Next.js to resolve symlinked packages outside the project directory.
+
+### Setup
+
+1. Link the package globally:
+   ```bash
+   cd mpackages/packages/mcreate
+   npm link
+   ```
+
+2. Link it in your Next.js project:
+   ```bash
+   cd your-nextjs-project
+   npm link mcreate
+   ```
+
+3. Update your projects `next.config.ts` to support external symlinks:
+   ```ts
+   import type { NextConfig } from "next";
+   import path from "path";
+
+   const nextConfig: NextConfig = {
+     transpilePackages: ['mcreate'],
+     outputFileTracingRoot: path.join(__dirname, "../"),
+   };
+
+   export default nextConfig;
+   ```
+
+   > **Note:** Adjust the `"../"` path to point to the common parent directory containing both your Next.js project and the mpackages folder.
+
+### Why is this needed?
+
+Turbopack (used by Next.js) doesn't support reading files or symlinks outside your project directory by default. The `outputFileTracingRoot` option expands the allowed directory scope to include the linked packages.

package/index.js

@@ -0,0 +1,7 @@
+function MaillowCreate() {
+  console.log('mcreate');
+
+  return "mcreate package is ready!";
+}
+
+module.exports = MaillowCreate;

package/package.json

@@ -0,0 +1,19 @@
+{
+  "name": "@kgalexander/mcreate",
+  "version": "0.0.2",
+  "description": "Maillow email template editor",
+  "main": "index.js",
+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Kga-6/mpackages.git#main"
+  },
+  "author": "Kevin Guerrero",
+  "license": "ISC",
+  "bugs": {
+    "url": "https://github.com/Kga-6/mpackages/issues"
+  },
+  "homepage": "https://github.com/Kga-6/mpackages/tree/main#readme"
+}