cherrytree - npm Package Versions

v2.4.1

• Fix a broken release, for some reason the npm run release failed to package correctly

v2.4.0

• Make it possible to transitionTo('anAbstractRoute') and generate('anAbstractRoute') in cases where the abstract route has a corresponding index route. This can be more intuitive in some cases.

v2.3.2

• URL encode slashes in route params

v2.3.1

• Don't intercept clicks on mailto: links

v2.2.1

• Fix: stop using Array.prototype.find which is not available in older browsers

v2.2.0

• Add router.isActive method for testing if a given route is currently active. See docs

v2.1.0

• Parse query params when transitioning even when no route matches

v2.0.0

Nothing changed from v2.0.0-rc4.

v2.0.0-rc4

• BrowserLocation and HistoryLocation can now be accessed at cherrytree.BrowserLocation and cherrytree.MemoryLocation again. This is to make it easier to use those modules for UMD users (#116).

v2.0.0-rc3

Breaking changes:

• HistoryLocation has been renamed to BrowserLocation. Location in cherrytree is the place that stores the current location of the app. Location is updated with the new path when cherytree transitions. Location also triggers updates when someone changes the location externally (e.g. by navigating with back/forward buttons or updating the URL). BrowserLocation is a more apt name since this location implementation represents browser's location bar and is configurable to use pushState or hashchange. This way, the other location that ships with cherrytree, MemoryLocation- also makes more sense, in this case we're saying the URL is simply stored in this in memory object and not really connected to the browser (which is what makes it useful on the server, for example).