wp_should_load_separate_core_block_assets

The timeline below displays how wordpress function wp_should_load_separate_core_block_assets has changed across different WordPress versions. If a version is not listed, refer to the next available version below.

WordPress Version: 6.5

/**
 * Checks whether separate styles should be loaded for core blocks on-render.
 *
 * When this function returns true, other functions ensure that core blocks
 * only load their assets on-render, and each block loads its own, individual
 * assets. Third-party blocks only load their assets when rendered.
 *
 * When this function returns false, all core block assets are loaded regardless
 * of whether they are rendered in a page or not, because they are all part of
 * the `block-library/style.css` file. Assets for third-party blocks are always
 * enqueued regardless of whether they are rendered or not.
 *
 * This only affects front end and not the block editor screens.
 *
 * @see wp_enqueue_registered_block_scripts_and_styles()
 * @see register_block_style_handle()
 *
 * @since 5.8.0
 *
 * @return bool Whether separate assets will be loaded.
 */
function wp_should_load_separate_core_block_assets()
{
    if (is_admin() || is_feed() || wp_is_rest_endpoint()) {
        return false;
    }
    /**
     * Filters whether block styles should be loaded separately.
     *
     * Returning false loads all core block assets, regardless of whether they are rendered
     * in a page or not. Returning true loads core block assets only when they are rendered.
     *
     * @since 5.8.0
     *
     * @param bool $load_separate_assets Whether separate assets will be loaded.
     *                                   Default false (all block assets are loaded, even when not used).
     */
    return apply_filters('should_load_separate_core_block_assets', false);
}

WordPress Version: 5.8

/**
 * Checks whether separate styles should be loaded for core blocks on-render.
 *
 * When this function returns true, other functions ensure that core blocks
 * only load their assets on-render, and each block loads its own, individual
 * assets. Third-party blocks only load their assets when rendered.
 *
 * When this function returns false, all core block assets are loaded regardless
 * of whether they are rendered in a page or not, because they are all part of
 * the `block-library/style.css` file. Assets for third-party blocks are always
 * enqueued regardless of whether they are rendered or not.
 *
 * This only affects front end and not the block editor screens.
 *
 * @see wp_enqueue_registered_block_scripts_and_styles()
 * @see register_block_style_handle()
 *
 * @since 5.8.0
 *
 * @return bool Whether separate assets will be loaded.
 */
function wp_should_load_separate_core_block_assets()
{
    if (is_admin() || is_feed() || defined('REST_REQUEST') && REST_REQUEST) {
        return false;
    }
    /**
     * Filters whether block styles should be loaded separately.
     *
     * Returning false loads all core block assets, regardless of whether they are rendered
     * in a page or not. Returning true loads core block assets only when they are rendered.
     *
     * @since 5.8.0
     *
     * @param bool $load_separate_assets Whether separate assets will be loaded.
     *                                   Default false (all block assets are loaded, even when not used).
     */
    return apply_filters('should_load_separate_core_block_assets', false);
}