Unable to run PG locally

Bugs
1

@RaananW

Hello!
I did a pull from usptream, npm i and ended up with tens of errors of this type: BABYLON is not defined

image
image2680Ɨ622 209 KB

2

How are you running this?

I mean, what command?

3

image
image872Ɨ144 12 KB

4

Then there must be an error in one of the pipeline. Anything failed assist from the playground?

5

image
image2332Ɨ982 444 KB

image
image2334Ɨ1002 503 KB

image
image2330Ɨ992 288 KB

Everything seems to be OK.

EDIT: Iā€™ll try npx build-tools --command dev-watch --watch-assets --watch-declarations --serve - SAME RESULTā€¦

6

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

7

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! :cool: :sun_with_face: :sunglasses: :beers: :cocktail: :beach_umbrella:

8

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

image

Nothing worked, I had to:

git reset --hard upstream/master to make it again working.