Viewing profile — aleclarsoniv
aleclarsoniv
HN member- Joined
- Tue, Mar 05, 2013, 3:26 AM UTC
- HN karma
- 71
- Public activity
- 49 items
- HN profile
- View on Hacker News ↗
About aleclarsoniv
Currently developing:
* radashi
* pg-nano
* alien-rpc
Currently maintaining:
* jumpgen
* alien-dom
Previously maintained:
* vite (core team from v0 til v4)
* immer (co-author)
* react-spring (co-author)
Recent public activity
-
story
Ask HN: Seeking feedback on my Postgres TypeScript thing
Hey HN! I'm the creator of pg-nano. It's not an ORM, a query builder, or a basic query driver, but it's closest to the last one. The twist is, it's also a migration tool and a code…
-
comment
Comment #42373344
Hey HN, I wrote this little library a while back. This may be a bit of a niche thing, since there hasn't been much prior art tackling this problem. Before making json-qs, I was usi…
- story
-
comment
Comment #42373304
I think it'd be worth looking at what's already out there before you put a lot of effort into this, unless of course this is merely for fun/learning.
- story
-
comment
Comment #42029461
I used this initially in a browser extension I'm building. Ended up migrating to a JSX library instead, because jQuery turns into hard-to-reason-about code pretty quickly once you'…
-
comment
Comment #41950479
I just published it now: https://www.npmjs.com/package/@json-qs/json-qs
-
comment
Comment #41945702
The most common case is probably complex search queries. It's really nice not having to flatten your data just to get network level caching. In my case, building an RPC library wit…
- story
- story
-
comment
Comment #41822562
The home feed is a poor experience, IMO. Adding a tagline to each product would help me know if I want to learn more, without having to decide to click based on a logo and name alo…
-
comment
Comment #41822133
I'd love to get everyone's feedback on this library I made. I've found it helps a lot when writing a library that takes advantage of compile-time code generation. In the future, I …
- story
-
comment
Comment #41799913
That's not entirely true. Tree-shaking algorithms could have a “noDynamicAccess” option that errors on such use (only viable for applications, not libraries). Alternatively, the al…
-
comment
Comment #41799858
* Not the creator of Terser, but the lead maintainer
-
comment
Comment #41794585
TypeBox[1] also supports bi-directional transforms. [1]: https://github.com/sinclairzx81/typebox
-
comment
Comment #41794549
TypeBox[1] differentiates between optional and undefined. [1]: https://github.com/sinclairzx81/typebox
-
comment
Comment #41794492
It requires flow analysis, which is really hard to get right. I don't think there's a tree-shaking library that uses the TypeScript compiler API for static analysis purposes. Maybe…
-
comment
Comment #41794441
I'd recommend TypeBox[1] as an alternative, which has a runtime “compiler” for generating optimized JS functions from the type objects. It also produces a JSON schema, which can be…
-
comment
Comment #41769632
I'd love to hear more about your experience with web discoverability, as I'm making a product that aims to help with that. Email me at alec.stanford.larson @ gmail I don't know if …
-
comment
Comment #41616929
That's not supported yet, but it will involve removing the foreign key constraint from one table (by parsing and rewriting the CREATE statement before running it). Then after the r…
-
comment
Comment #41616875
I wouldn't compare the two directly, as they serve different preferences. I would say that using Postgres functions is more powerful, but that may not matter for your app, dependin…
-
comment
Comment #41616829
You could use both side-by-side if you prefer query builders for certain tasks, but that means you'll be bundling two Postgres drivers in your application server, which could mean …
-
comment
Comment #41616807
> Seems like this tool could essentially pre-create the types for any raw Postgres SQL statement? It's a syntax parser that produces an AST. So only information explicitly defined …
-
comment
Comment #41587136
The main reason I didn't contribute my changes via PR is I wanted a package without "deparse" support, which adds considerably to the install size. I also didn't want pre-compiled …