Extract `@taskr/utils`?

Nobody has claimed this yet.

I'm sure if Taskr would benefit from exposing some of its tools directly.

The benefits would be that plugins could import/share some of the core Taskr helpers. Even though the [core utilities](https://github.com/lukeed/taskr/tree/master/packages/taskr#utilities) are exposed right now, we have a set of [internal helpers](https://github.com/lukeed/taskr/blob/master/packages/taskr/lib/fn.js) that could be part of this module too.

If this happens, the utilities would all be within the `@taskr/utils` package name.

Need your help deciding what I should do:

[](https://m131jyck4m.execute-api.us-west-2.amazonaws.com/prod/poll/01BMAYEAZ59VGX7R6BQ98XR8FB/Core%20Utilities%20only/vote)
[](https://m131jyck4m.execute-api.us-west-2.amazonaws.com/prod/poll/01BMAYEAZ59VGX7R6BQ98XR8FB/Internal%20Helpers%20only/vote)
[](https://m131jyck4m.execute-api.us-west-2.amazonaws.com/prod/poll/01BMAYEAZ59VGX7R6BQ98XR8FB/Expose%20BOTH/vote)
[](https://m131jyck4m.execute-api.us-west-2.amazonaws.com/prod/poll/01BMAYEAZ59VGX7R6BQ98XR8FB/Don't.%20No%20need/vote)

Comments welcome. Thanks! 😄

Start by comparing the core utilities documented in packages/taskr and the internal helpers in packages/taskr/lib/fn.js. The issue does not define which utilities to expose or provide a test or implementation entry point; the work is complete only after the package scope and exported helper set are decided.

Written by the indexing model from the issue text.