Summer Knight

fix(useInterval): use a memoized function

2

By memoizing the function via `useCallback` within `useInterval`, coupled with the explicit cache of `[]` (meaning that the effect only has an onMount and onUnmount), only a single interval is...

fix(useUnmount): use a memoized function

1

Because of the use of the `[]` cache, only the first function that was passed in would have been used during the unmount process. This ensures that the most recent...

Tests

1

How would you like to do testing of `react-pirate`? My first inclination is to use `jest`, have a sibling file for each hook, e.g. `useMount.test.js`, and within there, make one...

fix(ts): update Function types

1

This replaces the generalized `Function` with the more explicit `() => void`, which matches the actual API.

Unroll loops and data within toFunction()

2

This should be functionality equivalent to before, and the unit tests remain green. The resultant function should be much more friendly to the JITter, as it contains object accesses at...

There's no way that I can tell to escape user input within the template.

If one were to render a two user pages near-simultaneously with completely separate information in each sandbox, you will get repeated, bad data.

Since you have `config.cache = config.cache || exports.config.cache;`, you can't set cache to 0, you have to set it to a negative to get a similar effect.

I'd like to be able to configure this plugin such that: Bad: ```js const arrow = () => { return a ? b : c; // error because it's a...

Likely related to #1