feature/native-blocks #1

JoshuaCrewe commented 2025年12月19日 12:52:23 +01:00

This is sort of working at least in terms of a POC. There are a bunch of improvements I would make if the ecosystem would allow me to.

• Vite will not always auto compile code, sometimes it does it twice and then stops
• Block creation is currently more verbose than I want it to be (I'd rather not have index.js for each block)
• It is unreliable. Sometimes blocks will deregister (might be related to 1.)

This is sort of working at least in terms of a POC. There are a bunch of improvements I would make if the ecosystem would allow me to. - Vite will not always auto compile code, sometimes it does it twice and then stops - Block creation is currently more verbose than I want it to be (I'd rather not have index.js for each block) - It is unreliable. Sometimes blocks will deregister (might be related to 1.)

JoshuaCrewe commented 2025年12月19日 13:30:23 +01:00

I would like to upgrade the vite config to not fully rely on the rollup build but actually use the HMR. This would be more inline with what vite is expecting perhaps and might resolve the issue where the build isn't triggered reliably. Then we can do a single build for production.

We also need to update it to use the rolldown config as this will be coming in and I want to make sure the file names and rollup config get carried over or if I need to rewrite them

I would like to upgrade the vite config to not fully rely on the rollup build but actually use the HMR. This would be more inline with what vite is expecting perhaps and might resolve the issue where the build isn't triggered reliably. Then we can do a single build for production. We also need to update it to use the rolldown config as this will be coming in and I want to make sure the file names and rollup config get carried over or if I need to rewrite them

JoshuaCrewe commented 2026年03月01日 08:30:00 +01:00

As far as I know, the build system is working. There is an issue on one of my machines where the JS/TS files compile once under --watch. This appears to be an issue with the machine rather than the configuration. The same config works as expected for the hacking machine but not for the XPS. They are both on the same OS which are setup very similarly. It would be interesting to see what happens on a third machine. There is one other machine I have which is on the same OS and one which is MacOS.

To merge this :

• Confirm the two test blocks appear in the editor
• (削除) Enqueue styles to editor (削除ここまで)
• Be able to edit core block output
• Resolve formatting comments above
• Update paths to assets in enqueue function

As a bonus, if the HMR could be configured even if it can't be used it might be a solution to the problem machine. The reason I don't want it is because I don't want to have to keep the development server port open when working on multiple projects at the same time. To get it working we are looking at :

• Updating package.json to use vite watch
• Figuring out what the path on the dev server the assets are served at (this seems basically impossible)
• Create a PHP function to detect this mode and load via the above figured out URL
• Mode detection is best by looking for the hot file (make sure this is output to somewhere)

node : 25.6.1
https://github.com/paulmillr/chokidar?tab=readme-ov-file#getting-started

As far as I know, the build system is working. There is an issue on one of my machines where the JS/TS files compile once under --watch. This appears to be an issue with the machine rather than the configuration. The same config works as expected for the hacking machine but not for the XPS. They are both on the same OS which are setup very similarly. It would be interesting to see what happens on a third machine. There is one other machine I have which is on the same OS and one which is MacOS. To merge this : - [X] Confirm the two test blocks appear in the editor - [ ] ~~Enqueue styles to editor~~ - [X] Be able to edit core block output - [X] Resolve formatting comments above - [X] Update paths to assets in enqueue function As a bonus, if the HMR could be configured even if it can't be used it might be a solution to the problem machine. The reason I don't want it is because I don't want to have to keep the development server port open when working on multiple projects at the same time. To get it working we are looking at : - Updating package.json to use `vite watch` - Figuring out what the path on the dev server the assets are served at (this seems basically impossible) - Create a PHP function to detect this mode and load via the above figured out URL - Mode detection is best by looking for the hot file (make sure this is output to somewhere) ``` node : 25.6.1 https://github.com/paulmillr/chokidar?tab=readme-ov-file#getting-started ```

JoshuaCrewe commented 2026年03月02日 11:02:54 +01:00

@JoshuaCrewe wrote in #1 (comment):

As a bonus, if the HMR could be configured even if it can't be used it might be a solution to the problem machine. The reason I don't want it is because I don't want to have to keep the development server port open when working on multiple projects at the same time. To get it working we are looking at :

* Updating package.json to use `vite watch`
* Figuring out what the path on the dev server the assets are served at (this seems basically impossible)
* Create a PHP function to detect this mode and load via the above figured out URL
* Mode detection is best by looking for the hot file (make sure this is output to somewhere)

Issue created to address this in #3

@JoshuaCrewe wrote in https://codeberg.org/JoshuaCrewe/wordpress/pulls/1#issuecomment-11095271: > As a bonus, if the HMR could be configured even if it can't be used it might be a solution to the problem machine. The reason I don't want it is because I don't want to have to keep the development server port open when working on multiple projects at the same time. To get it working we are looking at : > > * Updating package.json to use `vite watch` > > * Figuring out what the path on the dev server the assets are served at (this seems basically impossible) > > * Create a PHP function to detect this mode and load via the above figured out URL > > * Mode detection is best by looking for the hot file (make sure this is output to somewhere) Issue created to address this in https://codeberg.org/JoshuaCrewe/wordpress/issues/3