This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.
⚠️⚠️⚠️⚠️⚠️⚠️
Releases
miniplex@2.0.0-next.11
Patch Changes
a886264: createComponents has been renamed to createReactAPI and is now the default export of both @miniplex/react and miniplex/react, in order to allow the user to pick a less terrible name. :-)
Updated dependencies [a886264]
Updated dependencies [b11083d]
Updated dependencies [43f9cae]
Updated dependencies [b11083d]
@miniplex/react@2.0.0-next.11
@miniplex/core@2.0.0-next.11
@miniplex/core@2.0.0-next.11
Patch Changes
b11083d: Aaaaah, another rewrite of the core library! @miniplex/core kept the same lightweight core, but the World is now much more aware of archetypes and what kind of entities they represent. This was done to allow for better introspection and to fix some remaining issues like #204].
The WithRequiredKeys type has been renamed to WithComponents.
Breaking Change:bucket.derive() has been removed. It was cool and fun and cute, but also a little too generic to be useful. Similar to Miniplex 1.0, there is only the world and a series of archetypes now. (But both share the same lightweight Bucket base class that can also be used standalone.)
43f9cae: Upgraded to a newer @hmans/event that uses .add and .remove instead of .addListener and .removeListener.
@miniplex/react@2.0.0-next.11
Patch Changes
a886264: createComponents has been renamed to createReactAPI and is now the default export of both @miniplex/react and miniplex/react, in order to allow the user to pick a less terrible name. :-)
43f9cae: Upgraded to a newer @hmans/event that uses .add and .remove instead of .addListener and .removeListener.
b11083d: <Archetype> has been changed to match the new query capabilities of the core library's world.archetype function. All of these are now valid:
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
main
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onmain
.⚠️⚠️⚠️⚠️⚠️⚠️
Releases
miniplex@2.0.0-next.11
Patch Changes
createComponents
has been renamed tocreateReactAPI
and is now the default export of both@miniplex/react
andminiplex/react
, in order to allow the user to pick a less terrible name. :-)@miniplex/core@2.0.0-next.11
Patch Changes
b11083d: Aaaaah, another rewrite of the core library!
@miniplex/core
kept the same lightweight core, but theWorld
is now much more aware of archetypes and what kind of entities they represent. This was done to allow for better introspection and to fix some remaining issues like #204].The
WithRequiredKeys
type has been renamed toWithComponents
.world.archetype()
now allows two forms:The second form involves a query object that can also have
any
andnone
keys:Breaking Change:
bucket.derive()
has been removed. It was cool and fun and cute, but also a little too generic to be useful. Similar to Miniplex 1.0, there is only the world and a series of archetypes now. (But both share the same lightweightBucket
base class that can also be used standalone.)43f9cae: Upgraded to a newer
@hmans/event
that uses.add
and.remove
instead of.addListener
and.removeListener
.@miniplex/react@2.0.0-next.11
Patch Changes
createComponents
has been renamed tocreateReactAPI
and is now the default export of both@miniplex/react
andminiplex/react
, in order to allow the user to pick a less terrible name. :-)@hmans/event
that uses.add
and.remove
instead of.addListener
and.removeListener
.b11083d:
<Archetype>
has been changed to match the new query capabilities of the core library'sworld.archetype
function. All of these are now valid: