First router 'nav' event is fired before listeners have subscribed
pottedmeat opened this issue · comments
Bug
The history manager is registered with an onChange
listener in the constructor. This means that the _onChange
method may be fired within the constructor, emitting the 'nav'
event before listeners have been registered.
Previously, this was handled through a .start
method but could be a constructor option or use a queued event manager.
Package Version: latest
Code
router.on('nav', () => {
console.log('nav');
});
Expected behavior:
'nav'
should be logged on page load.
Actual behavior:
'nav'
is not logged on page load.