Represent fallible operations as Result or ResultAsync values in TypeScript and JavaScript.
npx skills add https://github.com/Montte-erp/montte-nx --skill neverthrow
Please help me install this Agent Skill. Skill: neverthrow Source: https://github.com/Montte-erp/montte-nx/tree/main/.agents/skills/neverthrow Command: npx skills add https://github.com/Montte-erp/montte-nx --skill neverthrow
Replace ad-hoc exceptions and try/catch with explicit, type-safe error values so developers cannot accidentally ignore failures and must handle errors at call sites.
Wrap a Promise-returning SDK call with ResultAsync.fromThrowable and handle the returned ResultAsync with match to convert errors into your application error type.
High-intent search queries and answers about installing and using this skill.
Type-safe error handling without try/catch blocks is achieved by representing fallible operations as Result or ResultAsync values, enforcing explicit error handling at call sites. You compose operations using methods like map, mapErr, and andThen to handle success or failure states.
The best way to wrap Promise-returning SDK calls is using ResultAsync.fromThrowable or fromPromise. This converts exceptions or rejected promises into ResultAsync values, allowing you to handle errors safely without try/catch and convert them into application error types.
Functional error handling for async database operations works by wrapping repository work in ResultAsync<AppError> values. Web routers consume these results and convert errors to WebAppError directly, eliminating ad-hoc exceptions and ensuring failures cannot be accidentally ignored.
Yes, you can enforce Result consumption using an ESLint plugin integration. This ensures developers handle type-safe error values at call sites and cannot accidentally ignore failures, satisfying requirements for strict error handling in TypeScript and JavaScript code.
Yes, TypeScript functional error handling supports parallel async operations with short-circuit or error collection semantics. You combine parallel ResultAsync operations to either stop on the first error or aggregate all errors, ensuring type-safe failure management.
You eliminate boilerplate early returns when chaining type-safe error values by using the safeTry generator-based do-notation. This allows you to write sequential Result or ResultAsync logic without manual early returns for failure cases.
mouayadakelEnforce strict TypeScript standards by eliminating `any` and ensuring null handling.
btabaskaDiagnose API error responses and map 4xx/5xx status codes in Simpler.Grants.gov.
manutejEnforce strict typing and functional patterns in TypeScript with fp-ts.
cometkimMigrate try/catch and Promise rejections to typed Result flows with better-result.
