Skip to content

Conversation

@jilani53
Copy link
Contributor

@jilani53 jilani53 commented Oct 22, 2025

A fatal error occurred while using WordPress Directory version 3.20.0, which has now been fixed.
Error screenshot - https://prnt.sc/RvCJ_r3KcrZJ

@johnbillion
Copy link
Owner

Thanks for the PR @jilani53!

As you can see from the static analysis errors, it should never be possible for a script module to not include dependencies.

  • Has something changed in 6.9?
  • Can you provide example wp_enqueue_script_module() or wp_register_script_module() code from your site that is causing this problem?

Thanks!

@desrosj
Copy link

desrosj commented Oct 22, 2025

Just wanted to note that I also noticed this on my site today. I run the nightly build, and currently on 6.9-beta1-61042. Nothing changed between yesterday and today except the the changes made leading up to beta 1 being included in the latest nightly.

@johnbillion
Copy link
Owner

Thanks. I can reproduce this on my test site too, it was introduced in https://core.trac.wordpress.org/ticket/63486 . I'll take a proper look.

@johnbillion johnbillion added this to the 3.20.1 milestone Oct 22, 2025
@johnbillion johnbillion merged commit b89548f into johnbillion:develop Oct 23, 2025
45 of 46 checks passed
@johnbillion
Copy link
Owner

Thanks both! This is fixed and I'll get a release out shortly.

@johnbillion
Copy link
Owner

The change in 6.9 beta 1 that caused this has been reverted in beta 2 so it's no longer an issue.

We've got https://core.trac.wordpress.org/ticket/60597 for exposing a proper public API for enqueued modules.

@johnbillion johnbillion removed this from the 3.20.1 milestone Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants