Skip to content

Releases: junga-com/bg-dom

v2.3.8

30 Sep 21:43

Choose a tag to compare

  • 2 minor fixes to new GlobalServices module * used global Symbol.for(.. for the version attribute so that its the same attribute for multiple copies of bg-dom * PkgInfo -- was incorrectly appending -dev to production atom packages b/c they are not in a node_modules/ folder 6056bf3

v2.3.7...v2.3.8

v2.3.7

30 Sep 13:26

Choose a tag to compare

  • fixed global/multi-pkg instance bug in registering ChannelNode classes 96b4af1

v2.3.6...v2.3.7

v2.3.6

30 Sep 05:10

Choose a tag to compare

  • Finished the initial GlobalServices API * provides 2 new patterns 1) safely create global variables, and 2) track package loads to create bg.pkgInfo to analyze versions of the same package a6a33d1

v2.3.5...v2.3.6

v2.3.5

29 Sep 21:03

Choose a tag to compare

  • still working with the global services issue - publishing to test production vs dev * added GlobalServices.js to encapsulate pattens for sharing the gloabal namespace with versioning of APIs * 3d4d845

v2.3.4...v2.3.5

v2.3.4

29 Sep 03:10

Choose a tag to compare

  • think I found the correct pattern for the global problem. 55f08ff

v2.3.3...v2.3.4

v2.3.3

29 Sep 01:48

Choose a tag to compare

  • still working on global problem when multiple bg-dom exists 48b8ed1

v2.3.2...v2.3.3

v2.3.2

29 Sep 01:05

Choose a tag to compare

  • tracking down suspected global bug with split bg-dom dependency modules 0e49a27

v2.3.1...v2.3.2

first after renaming from bg-atom-redom-ui

28 Sep 22:36

Choose a tag to compare

This is the first release after renaming from bg-atom-redom-ui to bg-dom. There was an 'np' tool bug that prevented the first attempt from completing cleanly so that is why this .1 patch is just a minor change.

  • cleaning up multiple packages for publishing * passed {mount,unmount} exports through from redom so that packages that use us dont need to be dependent on redom pkg also 305a91d

v2.3.0...v2.3.1