Hello!
I did a pull from usptream, npm i and ended up with tens of errors of this type: BABYLON is not defined
How are you running this?
I mean, what command?
Then there must be an error in one of the pipeline. Anything failed assist from the playground?
Everything seems to be OK.
EDIT: I’ll try npx build-tools --command dev-watch --watch-assets --watch-declarations --serve - SAME RESULT…
The error you ate getting is from the console? Can you reach the BABYLON namespace? is everything loaded correctly in the network tab?
I’m away at the moment (will be for the next week and a half), but i might have access to a laptop in an hour or two. I’ll try running it with a fresh clone of the repo
I can’t reach it (BABYLONX is available) and there are no network errors.
You don’t need to do it. I did it and it works as expected.
I’ll try to figure out what’s causing the issue. If I’ll be not able to find the problem, I will transfer my current changes to a fresh repo.
Don’t bother with this and Enjoy your holiday! 
localhost:1338 doesn’t work but no errors when I access the PG at 127.0.0.1:1338.
EDIT: it loads the remote librariers, that’s why it works…
Still couldn’t load them properly from localhost:1337
Nothing worked, I had to:
git reset --hard upstream/master to make it again working.
1 Like