The package exists on npm registry (latest version 2.0.2), so the issue appears to be with the CDN/storage layer serving an empty file.