file_get_contents() error: wp-emoji-loader.js missing in formatting.php line 5967

[rollybueno]

Bug Report

Description

Describe the bug.

Environment

• WordPress: 6.9-alpha-60093-src
• PHP: 8.2.28
• Server: nginx/1.29.0
• Database: mysqli (Server: 8.4.5 / Client: mysqlnd 8.2.28)
• Browser: Chrome 137.0.0.0
• OS: Linux
• Theme: Twenty Twenty 2.9
• MU Plugins: None activated
• Plugins:
  • Query Monitor 3.18.0
  • Test Reports 1.2.0

Steps to Reproduce

1. Pull latest trunk. As of this writing, it's on ​https://github.com/WordPress/wordpress-develop/commit/7cf0bb5594ab336a2c919958378035e4bbf46db4
2. Open front-end in incognito - you should see:

   Warning: file_get_contents(/var/www/src/wp-includes/js/wp-emoji-loader.js): Failed to open stream: No such file or directory in /var/www/src/wp-includes/formatting.php on line 5967
   

3. Exact code that calls to p-emoji-loader.php: ​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/formatting.php#L5967
4. Try to switch to different official themes and you still see the error.
5. Looking at /wp-includes, there's no js directory there as of this writing:

24. 🐞 Bug occurs.

Expected Results

1. ✅ Expected file should exists.

Actual Results

1. ❌ What actually happened.

Additional Notes

• Just pull latest synced trunk.
• Switching to different theme does not work.

Supplemental Artifacts

• Exact code that calls to the file: ​https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/formatting.php#L5967
• wp-includes has no js subdirectory.
• front-end:

[westonruter]

Did you run a build? You need to do npm run build:dev. See ​https://github.com/WordPress/wordpress-develop?tab=readme-ov-file#to-start-the-development-environment-for-the-first-time

(I do wish this build step wasn't required.)

[vipulgupta003]

Hi @rollybueno,
I tried reproducing the issue using the same version of trunk as you mentioned, but I wasn’t able to replicate it on my end.
Is there anything specific you’ve set up or done differently that I might be missing?

​https://prnt.sc/E90xmaxZX3q9

[rollybueno]

Hey @westonruter,

Thanks, this never happens on my months old container even after countless trunk syncing before, not until early this morning. I used the npm run build:dev when resetting and rebuilding the container earlier but to no avail, thus falsely thought this was a bug on latest trunk merge then opened this ticket afterwards.

Using npm run dev fixed everything instead of that one. @vipulgupta003 thanks for looking this up. Closing here now

Cheers to both!