🔥 Remove assets config
This commit is contained in:
@@ -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'),
|
|
||||||
],
|
|
||||||
],
|
|
||||||
];
|
|
||||||
Reference in New Issue
Block a user