zapatos
proposal-intl-segmenter
Our great sponsors
zapatos | proposal-intl-segmenter | |
---|---|---|
4 | 5 | |
1,220 | 145 | |
- | 0.7% | |
7.1 | 0.0 | |
17 days ago | over 2 years ago | |
TypeScript | HTML | |
GNU General Public License v3.0 or later | - |
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.
zapatos
- Zapatos: Zero-Abstraction Postgres for TypeScript
-
Announcing a new TypeScript ORM
Requiring the user to define model classes for the "ORM" is a massive pain in large codebases and requiring the user to maintain these is just too much boilerplate. Seems extremely bloated compared to the simplicity of how the shortcuts are implemented in Zapatos or similar libraries where 90% of the code is compiled away for production.
-
Prisma ORM: how to use the great database mapping package
Take a look at https://github.com/gajus/slonik and https://github.com/jawj/zapatos
-
The complete guide to working with strings in modern JavaScript
I’m surprised to see no mention of tagged literals, a much more complex version of template literals. For users they may seem ~like a function call without parentheses. But they do quite a bit more.
Short version: they accept an array of raw substrings and a variadic set of arguments corresponding to the runtime values provided in template positions, each positional value corresponding following the raw string preceding it.
That raw array is more than what it seems, it also has a getter of raw string values for the template expressions. This is what String.raw (also not mentioned) uses to treat those arguments essentially the same way an untagged template literal would.
It’s an odd design/interface but it can be used to do some pretty cool stuff. For example, Zapatos[1], a type-safe SQL library for TypeScript.
My only complaints:
- I can’t think of a real reason for it to be variadic, and this makes authoring them a little more error prone. You should be able to expect one array of strings with a length N, and one array of (type checkable/inferrable) values with a length N-1.
2. Likewise I can’t think of a real reason for the raw values to be bolted onto a weird array subclass. It could just as easily have been an iterable third argument.
1: https://github.com/jawj/zapatos
proposal-intl-segmenter
-
String encodings
Splitting by grapheme clusters (or the characters the user actually sees): JS doesn't support this natively, so you'll need a library like grapheme-splitter. There's a Stage-4 proposal in the works, though: Intl.Segmenter:
-
Updates from the 86th meeting of TC39
Intl.Segmenter: Unicode segmentation in JavaScript slides.
-
Is there no .reverse() method for a string like there is for an array?
But even that's not bulletproof. The best method is to divide the string into grapheme clusters before reversing, which is where Intl.Segmenter comes in.
-
The complete guide to working with strings in modern JavaScript
Exactly, and emoji are outside the BMP, so it's not exactly an edge case, but the norm where two code units (UTF-16 double-bytes) are used to make one code point (Unicode character).
And it gets even worse, when you consider that for many purposes you're not even interested in code points but in graphemes -- e.g. a single visible emoji might actually be a combination of 5 code points, represented by 8 UTF-8 code units, taking up 16 bytes.
If you want to split a string by graphemes, you can either use the main dedicated library for it [3], or the relatively new API Intl.Segmenter [4] which is in Chrome and Safari, but still hasn't made it to Firefox [5].
[1] https://blog.jonnew.com/posts/poo-dot-length-equals-two
[2] https://www.contentful.com/blog/2016/12/06/unicode-javascrip...
[3] https://github.com/orling/grapheme-splitter
[4] https://github.com/tc39/proposal-intl-segmenter
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=1423593
-
Emoji under the hood
Also potentially (but not in practice so far) locale-specific. See the FAQ on Javascript's implementation: https://github.com/tc39/proposal-intl-segmenter#why-should-we-pass-a-locale-and-options-bag-for-grapheme-boundaries-isnt-there-just-one-way-to-do-it
What are some alternatives?
MikroORM - TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, MariaDB, MS SQL Server, PostgreSQL and SQLite/libSQL databases.
compressed-emoji-shortcodes - A Quest to Find a Highly Compressed Emoji :shortcode: Lookup Function
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
grapheme-splitter - A JavaScript library that breaks strings into their individual user-perceived characters.
docs - 📚 Prisma Documentation
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
orchid-orm - Orchid ORM
proposal-error-cause - TC39 proposal for accumulating errors
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
proposal-call-this - A proposal for a simple call-this operator in JavaScript.
proposal-source-phase-imports - Proposal to enable importing modules at the source phase