Move SW headers into Next config

gladly-team · Sep 3, 2020 · a159e2e · a159e2e
1 parent 3aaf24c
commit a159e2e
Show file tree

Hide file tree

Showing 2 changed files with 19 additions and 15 deletions.
diff --git a/next.config.js b/next.config.js
@@ -58,6 +58,25 @@ const nextConfig = {
     ].filter(Boolean)
   },
 
+  async headers() {
+    return [
+      {
+        // This includes the base path: /newtab/service-worker.js
+        source: '/service-worker.js',
+        headers: [
+          {
+            key: 'Cache-Control',
+            value: 'no-cache',
+          },
+          {
+            key: 'Service-Worker-Allowed',
+            value: `${basePath}/`, // e.g., /newtab/
+          },
+        ],
+      },
+    ]
+  },
+
   webpack: (config, options) => {
     // Sentry error logging. See:
     // https://github.com/vercel/next.js/blob/canary/examples/with-sentry-simple/next.config.js

diff --git a/vercel.json b/vercel.json
@@ -7,20 +7,5 @@
   "trailingSlash": true,
   "rewrites": [
     { "source": "/v4/(.*)", "destination": "/newtab/$1" }
-  ],
-  "headers": [
-    {
-      "source": "/newtab/service-worker.js",
-      "headers": [
-        {
-          "key": "Cache-Control",
-          "value": "no-cache"
-        },
-        {
-          "key": "Service-Worker-Allowed",
-          "value": "/newtab/"
-        }
-      ]
-    }
   ]
 }