wppaste
WordPress

WP_Dependencies::add( string $handle, string|false $src, string[] $deps = array(), string|bool|null $ver = false, mixed $args = null ): bool

Since
2.1.0, 2.6.0
Source
wp-includes/class-wp-dependencies.php:281
Register an item.

Description

Registers the item if no item of that name already exists.

Compatibility

WordPress
since 2.6.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$handlestring
Name of the item. Should be unique.
$srcstring|false
Full URL of the item, or path of the item relative to the WordPress root directory. If source is set to false, the item is an alias of other items it depends on.
$depsstring[]optional
An array of registered item handles this item depends on.
Default empty array.Default: array()
$verstring|bool|nulloptional
String specifying item version number, if it has one, which is added to the URL as a query string for cache busting purposes.
If version is set to false, a version number is automatically added equal to current installed WordPress version.
If set to null, no version is added.Default: false
$argsmixedoptional
Custom property of the item. NOT the class property $args.
Examples: $media, $in_footer.Default: null

Return value

bool
Whether the item has been registered. True on success, false on failure.

Performance profile

How much work a call to WP_Dependencies::add() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
9–36

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 40.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
0

Nothing in core calls this; the cost is only what you spend yourself.

What one call costs · 2 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Dependencies::add() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always9–22none
!isset($handle) && $handle31–36->enqueue()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 40 instructions, 9–36 executed per call, 3 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 2

Source code

	public function add( $handle, $src, $deps = array(), $ver = false, $args = null ) {		if ( isset( $this->registered[ $handle ] ) ) {			return false;		}		$this->registered[ $handle ] = new _WP_Dependency( $handle, $src, $deps, $ver, $args ); 		// If the item was enqueued before the details were registered, enqueue it now.		if ( array_key_exists( $handle, $this->queued_before_register ) ) {			if ( ! is_null( $this->queued_before_register[ $handle ] ) ) {				$this->enqueue( $handle . '?' . $this->queued_before_register[ $handle ] );			} else {				$this->enqueue( $handle );			} 			unset( $this->queued_before_register[ $handle ] );		} 		return true;	}

Changelog

Introduced in 2.1.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

2.6.0
Moved from WP_Scripts.from the docblock
2.1.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, from src/wp-includes/class-wp-dependencies.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.