v0.4.4

This release fixes two issues:

1. solid/reactivity now keeps track of which reactive primitives are imported from Solid and acts on those. This means you can import { createSignal as makeMeASignal } and the rule will still work correctly, and imports from other libraries with conflicting names will be ignored. #6
2. solid/reactivity now doesn't automatically warn when passing reactive variables to custom hooks. This decision puts a certain amount of trust in the programmer, as it is still a mistake to pass a reactive variable to a custom hook if the custom hook doesn't use it in a tracking scope. Rule of thumb: if you move the custom hook inline and it warns, there's a problem; if not, it's probably okay. #8

Full Changelog: v0.4.3...v0.4.4