fix: use JavaScript config instead of TypeScript for better CI compatibility

Author: rmitts

.github/workflows/deploy.yml

@@ -41,28 +41,8 @@ jobs:
         env:
           NODE_ENV: production
 
-      - name: Check build output
-        run: |
-          echo "Checking build output..."
-          ls -la
-          if [ -d "./out" ]; then
-            echo "✓ out directory exists"
-            ls -la out/
-          else
-            echo "✗ out directory does not exist, checking .next..."
-            ls -la .next/ || echo "No .next directory"
-            echo "Checking if build completed..."
-          fi
-      
       - name: Add .nojekyll file
-        run: |
-          if [ -d "./out" ]; then
-            touch ./out/.nojekyll
-            echo "✓ .nojekyll file created"
-          else
-            echo "Error: out directory does not exist"
-            exit 1
-          fi
+        run: touch ./out/.nojekyll
 
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3

next.config.ts next.config.jsnext.config.ts renamed to next.config.js

@@ -1,6 +1,5 @@
-import type { NextConfig } from "next";
-
-const nextConfig: NextConfig = {
+/** @type {import('next').NextConfig} */
+const nextConfig = {
   output: 'export',
   trailingSlash: true,
   images: {
@@ -10,4 +9,4 @@ const nextConfig: NextConfig = {
   assetPrefix: '/business-design-kit'
 };
 
-export default nextConfig;
+module.exports = nextConfig;