Checks whether separate styles should be loaded for core blocks on-render.

Description

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 also

• wp_enqueue_registered_block_scripts_and_styles()
• register_block_style_handle()

Return

Source

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 );
}

View all references View on Trac View on GitHub

Hooks

apply_filters( ‘should_load_separate_core_block_assets’, bool $load_separate_assets )

Filters whether block styles should be loaded separately.

Changelog