Consider moving `Hasher` package into `Crypto`

Description

Contributor guide

Tech stack

typescript

Domain

backendtooling

Issue type

refactor

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

needs maintainer response

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

needs investigation

Prerequisites

Understanding of @fuel ts/hasher and @fuel ts/crypto packagesFamiliarity with TypeScript module structure

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

Review the current structure of both packages in the repository. Check for dependencies between @fuel ts/hasher and @fuel ts/crypto. Look for any existing import usage of hasher functions across the SDK. Consider if moving would break imports and how to update package.json exports. The issue body is minimal, so checking linked PRs or comments (none listed) may be needed to clarify scope.