v4.3.3

4.3.3 (2020-07-18)

Bug Fixes

• deep-object-assign: prohibit console.log (#446) (d859cbd)

v4.3.2

4.3.2 (2020-06-15)

Bug Fixes

• ts: missed readonly fix in previous PR (#386) (e5e9aa9)

v4.3.1

4.3.1 (2020-06-15)

Bug Fixes

• ts: change readonly array syntax to support older tsc (#385) (59eefd7)

v4.3.0

4.3.0 (2020-06-14)

Features

• deep-object-assign: add pure version (#383) (c19d1f1)

v4.2.0

4.2.0 (2020-06-13)

Features

• deep-object-assign: improve type safety (#380) (6dc44c9)

v4.1.0

4.1.0 (2020-06-06)

Features

• add deep object assing with delete functionality (#321) (ce5c536)

v4.0.2

4.0.2 (2020-05-17)

Bug Fixes

• deps: update dependency vis-dev-utils to v2.2.13 (#301) (ece3e76)

v4.0.1

4.0.1 (2020-05-16)

Bug Fixes

• deps: update dependency vis-dev-utils to v2.2.10 (#297) (e895072)

v4.0.0

4.0.0 (2020-02-29)

• feat(build)!: use common build process (#144) (6a52bca), closes #144 visjs/vis-dev-utils#10

BREAKING CHANGES

• The old bundles are no longer present in the package. It has to be replaced by import * as util from 'vis-util/esnext';. I'll do that in all of our projects so don't bother updating to this, it most likely won't work anyway.

v3.0.0

3.0.0 (2020-02-19)

• feat(uuid)!: don't reexport UUID (#128) (7f95b27), closes #128

BREAKING CHANGES

• There's no randomUUID function anymore.

It was simply renamed and reexported. I don't really see the advantage
in this. Timeline and Network will have to use the uuid package
directly:

import { default as randomUUID } from "uuid/v4";

instead of

import { randomUUID } from "vis-util";

We export this from our builds but AFAIK it's all undocumented. Do we
consider this to be a part of the public API? If so this should probably
be posponed and deprecation warning added in the mean time to give
people more time to adjust.