Setting "bed_works" to "true" in non-"natural" dimension_type settings, and then sleeping, crashes the game

Overwriting the End's dimension_type settings via datapack and setting the "bed_works" field to "true," or creating a custom dimension with "bed_works" enabled and "natural" set to "false," causes the game to crash when a bed is used in the dimension in question. Have not tested this with the Nether, but presumably the outcome is similar. Crash report attached.

Steps to reproduce:

Download the attached datapack, install it in a world you aren't particularly attached to, enter the End, place a bed, and right-click.

Outcome: The game crashes with an 

Unexpected error: java.lang.NullPointerException: Cannot invoke "qv.a(qv$b, rc)" because "$$0" is null

Expected behavior: Ideally, the game would not crash. Presumably nothing else would happen, as the End is permanently locked to noon and thus the player should not be able to sleep in the first place. It probably shouldn't set the player's spawn point, as this could lead to them becoming trapped in the End, but it would be nice if it didn't explode. I do not recall this being the case in 1.17.