Releases: empiricaly/empirica
@empirica/core@1.9.8
Patch Changes
- 9e24313: Fix an issue with the shared/ignore lobby configuration, and more generally with
a number of players in a game that is not equal to thetreatment.playerCount
.
@empirica/core@1.9.7
@empirica/core@1.9.6
Patch Changes
- 0c39a7c: New export to fix consistency and performance issues.
@empirica/core@1.9.5
Patch Changes
- e70565d: Fix broken export command.
@empirica/core@1.9.4
Patch Changes
- 40a5d5c: Improve callback ordering by only allowing 1 callback to run at a time. This is
change also make addScopes await for the scope changes to be added locally
before returning. - 0994940: Enable
empirica serve
to run in the official Docker container image. - aa7fd43: Log connection errors instead of throwing unhanded exceptions.
- 434e36a: Avoid blocking on concurrent release of step stopping timer.
@empirica/core@1.9.3
Patch Changes
- fba5e09:
empirica serve
now respects the version in the bundle.
@empirica/core@1.9.2
Patch Changes
- 6974fe8: Upgrade node build to 20.10.0.
@empirica/core@1.9.1
Patch Changes
- fe46f00: Export vector attributes to CSV as arrays.
@empirica/core@1.9.0
Minor Changes
-
cd48506:
empirica export
could fail with a "Premature close" error (#474). This seems
to be originating from a bug in thenode-fetch
package, which is used to
polyfillfetch
in Node.js. This upgrades Node.js to v20+, which includes
nativefetch
support. We still have thecross-fetch
polyfill for projects
that have not updated to Node.js v20+ yet. Export uses a vendored project which
has been updated to use the latest Node.js version, so it does not require the
entire experiment to be updated for it to use Node.js v20+.See the following issues on
node-fetch
for more details:
node-fetch/node-fetch#1767
node-fetch/node-fetch#1576
Patch Changes
- b32b95a: Scoped objects should never be missing under EmpiricaContext. Some have reported
player.stage
orplayer.round
being undefined, for example. This fix also
more thoroughly checks that all expected objects (not only scoped objects) are
always present.
@empirica/core@1.8.12
Patch Changes
-
c20ca73: Fix setting attributes with the same mutated object as the current one.
For example, before this patch, the value would not be saved, since we are
reusing the same object, which we've only mutated in place:const value = player.get("myobject"); value["mykey"] = "myvalue"; player.set("myobject", value);
-
d1816ad: Ensure
usePlayers
never returns undefined (expect in unmanaged games).