# Cannot find namespace 'BABYLON' in TypeScript Playground

**URL:** https://forum.babylonjs.com/t/cannot-find-namespace-babylon-in-typescript-playground/50445
**Category:** Questions
**Tags:** playground, typescript
**Created:** [May 10, 2024, 10:35am UTC](https://forum.babylonjs.com/t/cannot-find-namespace-babylon-in-typescript-playground/50445 "2024-05-10T10:35:47Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![frazard99](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/frazard99/32/39632_2.png) [@frazard99](https://forum.babylonjs.com/u/frazard99)
#### Post date: [May 10, 2024, 10:35am UTC](https://forum.babylonjs.com/t/cannot-find-namespace-babylon-in-typescript-playground/50445/1 "2024-05-10T10:35:47Z")

</div>

Hello, the TypeScript Playground seems to be broken, but the JavaScript one is working.  
Here’s a screenshot of the issue:

 ![image](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/3X/e/b/ebd7c84f9d4dad4604f2072dbc1ba459632ce0bb.png)

I also tried to Disable Cache with the DevTools, but I had no luck 🙁

---

<div class="post-metadata">

### Author: ![Tricotou](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/tricotou/32/5844_2.png) [@Tricotou](https://forum.babylonjs.com/u/Tricotou)
#### Post date: [May 10, 2024, 11:23am UTC](https://forum.babylonjs.com/t/cannot-find-namespace-babylon-in-typescript-playground/50445/2 "2024-05-10T11:23:43Z")

</div>

Welcome on the forum 🙂

Please to a research before posting 😉 ➡ [Investigation in Progress about broken TS](https://forum.babylonjs.com/t/typescript-playgrounds-broken/50426)

++  
Tricotou

---

<div class="post-metadata">

### Author: ![frazard99](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/frazard99/32/39632_2.png) [@frazard99](https://forum.babylonjs.com/u/frazard99)
#### Post date: [May 10, 2024, 11:30am UTC](https://forum.babylonjs.com/t/cannot-find-namespace-babylon-in-typescript-playground/50445/3 "2024-05-10T11:30:35Z")

</div>

Oops, I tried to search for the error code and I found a post from the February 20th , the one you linked didn’t appear in the search results. Thanks!