feat(plugins): create plugins package

[dk1a]

Stub so that boilerplate diffs and discussion don't have to be in the actual plugins PR

@roninjin10 I tried to account for #514 already

The idea with the dep chain: schema-type -> store -> world -> config -> world-plugins -> config defaults.
cli would be after config, and probably after config defaults.

cli and config separation is unimplemented.
config defaults is unimplemented, I think the ECS wrapper @ludens had in mind would fit here, as well as some more general default for any kind of tables

[alvrs]

good call on moving this to a separate PR!

[ludns]

I think the ECS wrapper @ludens had in mind would fit here

so would the ECS plugin basically hook into the default config and change stuff there when imported?
I specifically don't think we should have ECS stuff by default, but if an import is found in the config file (eg: mud/ecs) then it should be able to set a default config, do config rewriting (ie: go from components -> tables with some rewriting), and change the type of the createStoreConfig function (or maybe expose another entry function? maybe that would be easier).

[dk1a]

(or maybe expose another entry function? maybe that would be easier).

yeah I think a separate entry would be easier to both implement and see what's happening.
ecsConfig could then restructure the config and pass it to mudConfig to reuse most validation

ecs stuff would also be not so much a plugin, as config wrapper that uses plugins. Well it can have a dedicated plugin too if needed

[holic]

can we mark this private for now? or otherwise "hide" this from the lerna release flow so canaries can work until we have an actual package here?

[holic]

what kind of world plugins are we thinking about? have we considered how the plugin API will look?

[dk1a]

what kind of world plugins are we thinking about?

current modules, tsgen, prototypes

have we considered how the plugin API will look?

not in any details, I'll probably improvise a PR and we can go from there

[alvrs]

i'd propose waiting with merging this one until we have a clearer picture of the plugin system

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
mud	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 1, 2023 1:43pm

[dk1a]

Updated this to match other package.jsons and renamed to plugins because #679 is not specific to world, which is also just a plugin

[alvrs]

I think the order of operations should be

1. [WIP] local config types #1025
2. hooks
3. create separate plugin package (this)
4. move existing plugins out of world/store into this

So i'm gonna temporarily close this to declutter the PR list, but generally think this is good and we can just reopen when it's time to merge it