Ryan Atkinson

The exported names of the reactive Map, Set, and others conflict with platform globals

6

### Describe the problem I like the functionality of `svelte/reactivity`'s reactive classes that extend globals like `Map` and `Set`, and I appreciate terseness and aesthetics of naming them the same...

See these PRs where this was previously implemented, and then removed with the build system. - https://github.com/ryanatkn/gro/pull/283 - https://github.com/ryanatkn/gro/pull/382 Needs to be thought through in combination with Moss style optimizations....

see `https://github.com/oxc-project/oxc/issues/8369` and `https://github.com/oxc-project/oxc/issues/7788` todo - dynamic imports don't seem to be supported?

One of the few rough edges I notice often in Gro these days is the lack of types for `invoke_task`. - generate types so task name string+params are checked against...

[Oxc](https://github.com/oxc-project/oxc) is the future of SvelteKit and Vite, replacing [esbuild](https://github.com/evanw/esbuild) which has been good for my/Gro's usage. [Rolldown](https://github.com/rolldown/rolldown) will handle the server and worker bundling cases but it's not ready...