Mark Lundin

> How do you define a name of a script and attach it to the entity? Scripts will be identified by their path, so `entity.esmscript.import('./path/to/esmscript.js')`. I think this will make...

> assets in Editor are all located in a flat way, and do not follow asset folder structures, as folder assets are purely Editor organizational tool. There is work to...

Gotcha thanks! > > The import will be context aware and fetch the bundle if necessary and resolve the ESM script it export. It should also handle code splitting. If...

> I just tried to run the Misc/Hello-Script-Modules example and it errors: > Thanks @kungfooman, that's my oversight. It should be fixed now if you want to try again. I'm...

@willeastcott @slimbuck @mvaligursky @kungfooman @LeXXik @Maksims Any more thoughts here?

@Maksims I’ve opted for a separate system for a few reasons. We’re planning to allow a global script priority, so users can specify an execution order to types of scripts....

@kungfooman I'm AFK at the moment, but thanks for reviewing this all. Will get back to you both when I can. Appreciate all the work 🙏

To be honest, this has caused a few headaches in the past... ```JavaScript const c = Color() script.color = c c.r = 1 (script.color.r === 1) // nope ```

It would be great if we can remove the direct dependancy on the `node_modules` of the engine, and just symlink it directly using [npm workspace](https://docs.npmjs.com/cli/v7/using-npm/workspaces/) which doesn't require building the...

But `npm run build` in example doesn't work unless you build the engine first.