Netzo should meet developers where they already are: developing. The DX of netzo apps could be greatly improved by a plugin which mounts itself into /devtools (only during development, not during production). Nuxt DevTools is a great source of inspiration.
Netzo could then mount this within the app using <iframe src="http://localhost:8000/devtools" /> during development and if not present, prompt the developer to enable the plugin.
Implementation
There are 2 possible alternatives:
netzoDevTools: a plugin which auto serves itself. this makes MUCH more sense. Basically Nuxt DevTools but for Netzo. This would speed-up its development, promote code reuse, and make it IDE agnostic, and eventually even framework agnostic (e.g. Hono can be supported, the devtools plugins just needs to mount itself into /devtools.
vscode extension: would not be IDE-agnostic and it is also quite complicated to develop, plus it has certain limitations (it runs in another environment, not same as apps).
Motivation
Netzo should meet developers where they already are: developing. The DX of netzo apps could be greatly improved by a plugin which mounts itself into
/devtools
(only during development, not during production). Nuxt DevTools is a great source of inspiration.Netzo could then mount this within the app using
<iframe src="http://localhost:8000/devtools" />
during development and if not present, prompt the developer to enable the plugin.Implementation
There are 2 possible alternatives:
/devtools
.vscode extension: would not be IDE-agnostic and it is also quite complicated to develop, plus it has certain limitations (it runs in another environment, not same as apps).