
Research
Security News
Lazarus Strikes npm Again with New Wave of Malicious Packages
The Socket Research Team has discovered six new malicious npm packages linked to North Korea’s Lazarus Group, designed to steal credentials and deploy backdoors.
ts-error-as-value
Advanced tools
Any error-as-values library in typescript is liable for being used a lot within any project which adds it, so making the API as convenient as humanly possible was my primary concern.
The alternative typescript libraries for achieving errors-as-values all seem to have verbose and cumbersome APIs, often wrapping all returns with class instances, and asking you to call method on them such as "isOk" or "isErr" to function.
Instead of this, we leverage typescript's discriminated unions to handle most of the heavy lifting for us.
To further decrease friction for using this in your project, you can also import the functions and types of this package into your project's global scope in a convenient way.
yarn install ts-error-as-value
import "ts-error-as-value/lib/globals";
This will make the functions ok, err and withResult, as well as the types Success, Failure and Result globally available
Creating Success
and Failure
result objects
const { data, error } = ok("Hello");
if (error) {
// do something with error
} else {
// do something with data
}
or
const {data, error} = err(new Error("Error"));
if (error) {
// do something with error
} else {
// do something with data
}
Wrapping the returns from functions with err
for errors, and ok
for non-error so that the function calling it receives a Result
type.
// Specifying the return type here is optional, as it will be inferred without it
const fnWithResult = (): Result<string, Error> => {
if ("" !== "") {
return ok("hello");
}
return err(new Error("Method failed"));
};
const { data, error } = fnWithResult();
if (error) {
// is an error
} else {
// data is guaranteed to be a string here, and error is guaranteed to be null
}
Or with promises:
const fnWithResult = async (): Promise<Result<string, Error>> => {
if ("" !== "") {
return ok("hello");
}
return err(new Error("Method failed"));
};
const callsFnThatCallsFnWithResult = async () => {
const { data, error, errorStack } = (await fnWithResult())
if (error) {
return err(error);
}
return ok(data);
};
callsFnThatCallsFnWithResult();
Result
class NewError extends Error {}
const fnWithResult = (): Result<string, Error> => {
if ("" !== "") {
return ok("hello");
}
return err(new Error("Method failed"));
};
const callsFnThatCallsFnWithResult = async (): Promise<Result<boolean, NewError>> => {
const { data, error } = fnWithResult()
// Because of using mapErr below, error will be an instance of NewError if fnWithResult returns an error
.mapErr(error => new NewError("Failed to call fnWithResult"))
// Because of using andThen below, data will be boolean if fnWithResult returns a value.
.andThen(data => {
return data === "hello";
});
if (error) {
return err(error);
}
return ok(data);
};
One downside to using a system where errors are treated as values in javascript is that you have no control over whether a third party dependency will throw errors or not. As a result, we need a way to wrap functions that can throw errors and force them to return a result for us.
withResult is a function which wraps another function and returns a Failure
result if the wrapped function throws an error,
or a Success
result if the wrapped function does not.
import somePkg from "package-that-throws-errors";
const doStuff = withResult(somePkg.doStuff);
const { data, error } = await doStuff("hello");
if (error) {
// the function doStuff in the package threw an error
}
export type Failure<E extends Error = Error> = {
data: null,
error: E,
successOrThrow(): void, // Returns the value, but throws an error if the result is an Error
successOrDefault<D>(defaultValue: D): D, // Returns the value or gives you a default value if it's an error
transformOnFailure<E2 extends Error>(fn: (fail: E) => E2): Failure<E2>, // If the result is an error, map the error to another error
transformOnSuccess<N>(fn: (data: never) => N): Failure<E> // If the result is not an error, map the data in it
};
export type Success<T> = {
data: T,
error: null,
successOrThrow(): T, // Returns the value, but throws an error if the result is an Error
successOrDefault<D>(defaultValue: D): T, // Returns the value or gives you a default value if it's an error
transformOnFailure<E2 extends Error>(fn: (fail: never) => E2): Success<T>, // If the result is an error, map the error to another error
transformOnSuccess<N>(fn: (data: T) => N): Success<N> // If the result is not an error, map the data in it
};
export type Result<
T, E extends Error = Error
> = Failure<E> | Success<T>;
declare function ok<T = void>(data?: T): Success<T>;
declare function err<E extends Error>(error: E): Failure<E>;
// When the wrapped function returns a promise
function withResult<T, E extends Error, R>(
fn: (...args: T[]) => Promise<R>
): (
...args: T[]
) => Promise<Result<R, E>>
// When the wrapped function does not return a promise
function withResult<T, E extends Error, R>(
fn: (...args: T[]) => R
): (
...args: T[]
) => Result<R, E>
FAQs
Errors as values in typescript
The npm package ts-error-as-value receives a total of 276 weekly downloads. As such, ts-error-as-value popularity was classified as not popular.
We found that ts-error-as-value demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
The Socket Research Team has discovered six new malicious npm packages linked to North Korea’s Lazarus Group, designed to steal credentials and deploy backdoors.
Security News
Socket CEO Feross Aboukhadijeh discusses the open web, open source security, and how Socket tackles software supply chain attacks on The Pair Program podcast.
Security News
Opengrep continues building momentum with the alpha release of its Playground tool, demonstrating the project's rapid evolution just two months after its initial launch.