From 1e9790c37d876402882a44c3dd3f09050b19173c Mon Sep 17 00:00:00 2001
From: Ben Word <ben@benword.com>
Date: Wed, 12 Feb 2025 08:58:49 -0500
Subject: [PATCH] =?UTF-8?q?=F0=9F=94=A5=20Remove=20assets=20config?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 config/assets.php | 40 ----------------------------------------
 1 file changed, 40 deletions(-)
 delete mode 100644 config/assets.php

diff --git a/config/assets.php b/config/assets.php
deleted file mode 100644
index 54d5ffd..0000000
--- a/config/assets.php
+++ /dev/null
@@ -1,40 +0,0 @@
-<?php
-
-return [
-
-    /*
-    |--------------------------------------------------------------------------
-    | Default Assets Manifest
-    |--------------------------------------------------------------------------
-    |
-    | Here you may specify the default asset manifest that should be used.
-    | The "theme" manifest is recommended as the default as it cedes ultimate
-    | authority of your application's assets to the theme.
-    |
-    */
-
-    'default' => 'theme',
-
-    /*
-    |--------------------------------------------------------------------------
-    | Assets Manifests
-    |--------------------------------------------------------------------------
-    |
-    | Manifests contain lists of assets that are referenced by static keys that
-    | point to dynamic locations, such as a cache-busted location. We currently
-    | support two types of manifest:
-    |
-    | assets: key-value pairs to match assets to their revved counterparts
-    |
-    | bundles: a series of entrypoints for loading bundles
-    |
-    */
-
-    'manifests' => [
-        'theme' => [
-            'path' => get_theme_file_path('public'),
-            'url' => get_theme_file_uri('public'),
-            'bundles' => get_theme_file_path('public/build/manifest.json'),
-        ],
-    ],
-];