Math: Format and block trigger an error in WP 6.9

[Mamaduka]

I noticed that when running Gutenberg trunk with WP 6.9, the Math format triggers an error. The same error occurs when inserting the math block.

Uncaught (in promise) TypeError: Failed to resolve module specifier '@wordpress/latex-to-mathml'

gutenberg/packages/format-library/src/math/index.js

Lines 133 to 137 in d419b56

	useEffect( () => {
	import( '@wordpress/latex-to-mathml' ).then( ( module ) => {
	setLatexToMathML( () => module.default );
	} );
	}, [] );

gutenberg/packages/block-library/src/math/edit.js

Lines 35 to 51 in d419b56

	useEffect( () => {
	import( '@wordpress/latex-to-mathml' ).then( ( module ) => {
	setLatexToMathML( () => module.default );
	if ( initialLatex.current ) {
	__unstableMarkNextChangeAsNotPersistent();
	setAttributes( {
	mathML: module.default( initialLatex.current, {
	displayMode: true,
	} ),
	} );
	}
	} );
	}, [
	initialLatex,
	setAttributes,
	__unstableMarkNextChangeAsNotPersistent,
	] );

[Utsav-Ladani]

@Mamaduka It appears to be an issue with the importmap. It didn’t have a mapping for @wordpress/latex-to-mathml.

<script type="importmap" id="wp-importmap">
  {
      "imports": {
          "@wordpress/abilities": "http://localhost:8888/wp-content/plugins/gutenberg/build/modules/abilities/index.js?ver=f3475bc77a30dcc5b38d"
      }
  }
</script>

[Mamaduka]

@Utsav-Ladani, yeah, this is a regression. Noticed only recently; it was working without a problem.

[Utsav-Ladani]

@Mamaduka This line is deregistering the script:

gutenberg/packages/wp-build/templates/module-registration.php.template

Lines 29 to 33 in 53a2647

	// Deregister first to override any previously registered version
	// (e.g., Core's default modules when running as a plugin).
	wp_deregister_script_module( $module['id'] );

This PR description explains a reason of that change: #75909

[Mamaduka]

Good find, @Utsav-Ladani!

Looks like we're deregistering the script and never adding it back. cc @scruffian, @youknowriad

Maybe this is some issue as #76170.

[mcsf]

I can confirm that, for me, this issue appears with 2b8f161 (#75909). If using npm run dev to test, make sure to restart it after switching HEAD.

[ramonjd]

#76170 fixes this issue (and the reported vips module issue as well)

I just approved if folks want to double check.

[mcsf]

Can we close this one now? /cc @dlind1, who also reported this via DM

[dlind1]

@mcsf, I can confirm that this is fixed now.