feat: add functions folder to deploy (#134)

Co-authored-by: Joshua Morony <[email protected]>

Author: joshuamorony

src/deploy/index.ts

@@ -168,9 +168,20 @@ export default createBuilder(
             context.logger.info(
                 `Deploying project from 📂 ./${builderConfig.outputPath}`
             );
+
+            let config = {};
+
+            if (builderConfig.functionsPath) {
+                console.log(
+                    `Deploying functions from 📂 ./${builderConfig.functionsPath}`
+                );
+                config = { ...config, fnDir: builderConfig.functionsPath };
+            }
+
             const response = await client.deploy(
                 siteId,
-                builderConfig.outputPath
+                builderConfig.outputPath,
+                config
             );
             context.logger.info(
                 `✔ Your updated site 🕸  is running at ${response.deploy.ssl_url}`

src/deploy/schema.d.ts

@@ -3,9 +3,10 @@ export interface Schema {
     configuration?: string;
     noBuild?: boolean;
     outputPath?: boolean;
+    functionsPath?: boolean;
     netlifyToken?: string;
     siteId?: string;
     baseHref?: string;
     create?: boolean;
-    withDeps?: boolean
+    withDeps?: boolean;
 }

src/deploy/schema.json

@@ -23,6 +23,10 @@
             "type": "string",
             "description": "This is one of the options you can freely choose according to your needs. --- We will 'deploy' to this folder."
         },
+        "functionsPath": {
+            "type": "string",
+            "description": "Path to the functions folder you want to deploy"
+        },
         "netlifyToken": {
             "type": "string",
             "description": "Acess token give you the ability to communicate with netlify over API."