When registering blocks via register_block_type('block.json'), the asset path is wrong

[jakeparis]

I am building a theme and learning about the concept of registering blocks with register_block_type('block.json'). However, when I do, the script/style file asset paths are messed up. Any insights/pointers would be most appreciated as I learn this new way.

The editor seems to be trying to load a url based on
https://example.com/mysite/wp-content/plugins/
concatenated with the filesystem path to the block index file:
/shared/httpd/htdocs/wp-content/themes/jmc/build/blocks/jake/index.js?ver=192383983

So the end results look like:

• https://example.com/mysite/wp-content/plugins/shared/httpd/htdocs/wp-content/themes/jmc/build/blocks/jake/index.js?ver=c10b6a3ac45e2d11a234a6cd2c193a5c
• https://example.com/mysite/wp-content/plugins/shared/httpd/htdocs/wp-content/themes/jmc/build/blocks/jake/index.css?ver=5.9.3

Here's my block.json.

block.json

{
  ...
	"editorScript": "file:./index.js",
	"editorStyle": "file:./index.css",
	"viewScript": "file:./public.js",
	"style": "file:./public.css"
 }

I'm loading all the block.json files in a loop like so:

registration.php

foreach ( glob( get_stylesheet_directory() . "/build/blocks/*/block.json" ) as $file ) {
    register_block_type( $file );
}

My src directory is structured like so:

themedir
| - src
| - | - blocks
| - | - | - jake
| - | - | - | - block.json
| - | - | - | - index.js
| - | - | - | - index.scss
                 ...
| - build
| - | - blocks
| - | - | - jake
| - | - | - | - block.json
| - | - | - | - index.js
| - | - | - | - index.css
                 ...

[jakeparis]

This may be a problem because I am using this technique in a theme, not a plugin. I've filed a ticket: #40744

[jakeparis]

Nevermind, I solved the "override each other's output" issue by specifying --output-dir= in the build command.

[gziolo]

Nice, I'm glad you sorted it out. We will keep your use case in mind. It would be cool if you could have everything under control with a single commend and without a custom Webpack config file (which would be another option that other projects often use).

[kfathy194]

@jakeparis Hi
I have the exact same scenario as yours, can you please share the end solution?

[kmorepubli]

i have it here also

[gziolo]

What WordPress version and which platform do you use (Windows, macOS, linux)?