Today I learned about JSONL format

Search for a command to run...

No comments yet. Be the first to comment.
This apply the dependencies transformations needed, and add the PostCSS config file needed. npm remove @tailwindcss/vite npm remove tailwindcss npm install tailwindcss@3 @tailwindcss/forms npm install postcss autoprefixer cat > postcss.config.js ...

Warning: I just deprecated it. Claude Code is fantastic, it does the same job I wanted to achieve with this. It’s a CLI instead of an UI, but it does 10x or 100x more than the current application situation. Get it here: https://docs.anthropic.com/en/...

I know, Livewire and Tailwind are the base for Filament, and this tutorial is not any hidden gem, but my gut feeling tells me I should write it. It shows few steps of the docs, but many don't get there, and don't even know this is possible. Filament ...

You're reading this, so you want the Login page ready to go in local environments, without having to type in a default user (configured in your seeder). Let's go. Let's create a Filament Page. Press <enter> for an empty answer, when asked if the page...

Fun fact, while deep diving how Claude Code works, I realised some files were stored with a .jsonl format! What’s this, a typo?? 😀 Of course not….
It's a text format where each LINE is a valid JSON object. So why this and not just a JSON array?!
Regular JSON - one big array
[
{"id": 1, "name": "Alice"},
{"id": 2, "name": "Bob"}
]
JSONL - one object per line
{"id": 1, "name": "Alice"}
{"id": 2, "name": "Bob"}
Why?
- Logs and "file as database" -> just append!
- Reading with stream: we can parse each line, one by one, immediately! A slightly different array of objects!
And much more possibilities, I’m sure!
There are some things to take in consideration:
Not human-readable at a glance (no pretty formatting)
Can't have relationships between lines easily
Harder to edit manually
Less tooling support than regular JSON
I hope you enjoyed this nugget!! Happy coding!