Init side-effects

[dy]

1. It won't trigger initial onload for elements that are in DOM already:

import onload from "fast-on-load";
onload(document.body, () => console.log('on'), () => console.log('off'))
// silence in console

2. It triggers unload-only for elements present in both added/removed nodes:

let a = document.createElement(a)
onload(a, function () {
  console.log('on')
}, function () {
  console.log('off')
})

document.body.appendChild(a)
document.body.removeChild(a)

// logs only 'off' 

Just to make sure if that's planned behavior.

[mafintosh]

1. is working as designed.
2. good question what the intend is here. @bcomnes @emilbayes wdyt?

[bcomnes]

1. could go either way. If you want to support ssr then you probably need to make this an option. If you want to keep this as an editorialized constraint, keeping it as is buys some simplicity.

2. sounds like a bug in the general conceptual sense. It should fire both. Are we auto wrapping callbacks in micro tasks?