Open rdjpalmer opened 2 years ago
Alternatively, we should consider making no-persistence-mixpanel as small as possible, and allow for each method to be tree-shakable. E.g., if a project only uses mixpanel.track
then we should support treeshaking of all the other methods
The library currently opts to simplify the APIs into plain english. E.g.,
mixpanel.people.set
has becomemixpanel.setUserProperty
.We should use the same naming conventions and class structure so the library can be a drop in replacement instead