This is caused because of the order of the scripts in the section. Move the loaders file to be right after the code babylon module, and the error is gone.
I guess the solution would be to move the inspector to the end of the loading process. As we first load the scripts and only after analyze the code, the playground doesn’t have this issue at all.
Thanks ! yes this does solves it… this is new that the inspect depends on the loaders (or at least fails if not included) … It was hard to troubleshot for me because I had a project not requiring the loaders… and the inspector could load previously
Should I open an issue on github to at least put the inspector below the other in the playground to avoid other people running into it ?