proxy-lens VS boxed

Compare proxy-lens vs boxed and see what are their differences.


A type safe functional lens implemented via proxy (by aynik)


Utility types for functional TypeScript (by swan-io)
Our great sponsors
  • Appwrite - The open-source backend cloud platform
  • Onboard AI - Learn any GitHub repo in 59 seconds
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
proxy-lens boxed
2 6
2 565
- 0.5%
0.0 0.0
9 months ago 6 days ago
TypeScript TypeScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of proxy-lens. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning proxy-lens yet.
Tracking mentions began in Dec 2020.


Posts with mentions or reviews of boxed. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-13.
  • The gotcha of unhandled promise rejections
    5 projects | | 13 Jan 2023
    I was happy when Promise became available, but in retrospect I'd wish we would have skipped ahead and gotten Observable (e.g: instead to enable more powerful functionality and composition etc.

    In Typescript dealing with rejection is also painful since rejection reasons can't be guaranteed to be Error even when you always take care of that. And it can't help you guarantee that you're handling all types of errors thrown. For that purpose I'm thinking of using or

  • Boxed: Functional utility types and functions for TypeScript
    2 projects | /r/javascript | 27 Apr 2022
  • I Avoid Async/Await
    7 projects | | 16 Apr 2022
    Agree that try/catch is verbose and not terribly ergonomic, but my solution has been to treat errors as values rather than exceptions, by default. It's much less painful to achieve this if you use a library with an implementation of a Result type, which I admin is a bit of a painful workaround, but worth it. I've recently been using:

    By far the greatest benefit is being able to sanely implement a type-safe API. To me, it is utter madness throwing custom extensions of the Error class arbitrarily deep in the call-stack, and then having a catch handler somewhere up the top hoping that each error case is matched and correctly translated to the intended http response (at least this seems to be a common alternative).

What are some alternatives?

When comparing proxy-lens and boxed you can also consider the following projects:

async - Easily run code asynchronously

rescript-compiler - The compiler for ReScript.

variant - Variant types in TypeScript

async - Async utilities for node and the browser

htmx - </> htmx - high power tools for HTML

cofx - A node and javascript library that helps developers describe side-effects as data in a declarative, flexible API.

neverthrow - Type-Safe Errors for JS & TypeScript

posterus - Composable async primitives with cancelation, control over scheduling, and coroutines. Superior replacement for JS Promises.

redux-saga - An alternative side effect model for Redux apps

RxJS - A reactive programming library for JavaScript

rslike - Rust-like but for TypeScript/JavaScript