From 74acaca2a9364a7b8756e220757fef90fc661281 Mon Sep 17 00:00:00 2001
From: Ben Word <ben@benword.com>
Date: Thu, 6 Feb 2025 11:56:39 -0500
Subject: [PATCH] brb

This reverts commit b343e9060ae06241164a914e3cdcaa384d4be696.
---
 config/assets.php | 40 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 config/assets.php

diff --git a/config/assets.php b/config/assets.php
new file mode 100644
index 00000000..54d5ffd2
--- /dev/null
+++ b/config/assets.php
@@ -0,0 +1,40 @@
+<?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'),
+        ],
+    ],
+];