This functionality was always unnecessary, because the example could be done with a curried function for example:
```js
function makeEventListener(number) {
return (event) => console.log("button " + number + " was clicked!");
}
```
ISSUES FIXED: #988
This adds a new section to CONTRIBUTING.md that explains that we are
using conventional commits and that commithelper can be used to create
valid commit messages
The only secret that is configured is the access key for browserstack.
The worst case of getting it extracted is that someone can run tests on
browserstack with our account. The snabbdombot user has no admin
privileges, so in that case we can just issue a new access key
This is useful for bundlers. When dealing with reexports, this setting
allows e.g. webpack to optimize reexports. See the webpack documentation
for more information about this setting
The hero module is very specific and not really a good fit for a low
level library like snabbdom. Users that still want to use it can copy
the code from the hero example instead
ISSUES CLOSED: #517
BREAKING CHANGE:
Snabbdom does not export the hero module any more. If you require this
module, copy the code from examples/hero/hero.js and add it to your
project
3 tests are still failing for safari 9.1 at the moment. On safari 10.1
all the tests pass however. As El Captain is pretty old now, the tests
now run on Sierra. The current safari version is updated to 14
ISSUES CLOSED: #469
Chrome 49 was disabled in the browserstack tests because of failing
tests. Trying those tests now again, only a single CSS variable test is
failing. As chrome 49 was the first chrome version to support css
variables it is very likely that this is a bug in the browser itself,
especially as chrome 50 works as expected. Thus this commits enables the
browserstack tests for chrome 50
ISSUES CLOSED: #468
kyle
Censwin
Jan van Brügge
cary
Ryota Kameoka
Toby Mao
dependabot[bot]
shanyue
shanyue
Jan van Brügge
George Treviranus
Mike Reinstein