James

I was wondering about this the other day 😄 I lost track of the yaml language a bit but would love to see it built in. I wasn't aware people were using it!

Best costume 😀

Same!
I think for me it's because coding was always a hobby even when I started doing it as a job. So I'm just doing it for fun and learning pretty much

Spending the bus journey north doing @npmx.dev triage and code reviews of course 😄

I don't believe we've ever acted as a closed community. Fundamentally, we are open and strive to be. That is how we are able to reach people and how we can help improve the ecosystem.

This thread has become extremely exhausting and narrow so I'm going to step away now.

Hmm not quite. As I said before, I'm not saying you're right or wrong. How you perceive things is up to you.

We're down a bit of a rabbit hole now I think!
The e18e community is certainly very open and very public. Nobody wants to hide it. The whole point is to make these efforts public and help people improve their own projects through that

You seem to have misunderstood. I'm not saying your perception is invalid. Regardless of how it is perceived, nobody tried to hide our community. You can perceive it however you like, each to their own

I understand you perceived it as deception. I'm just pointing out that it wasn't deception (even if you perceived it as such). Nobody is trying to hide e18e, we are all proud of our achievements

Made it to Toronto! 🥳

What do you want to change my mind about?

I know nobody was trying to hide e18e or be deceptive. If you think someone was, I can't do much about that knowing they weren't

Fair enough 👍
Well nobody in e18e was trying to be deceptive, and none of us were ever trying to "hide" the community.
It seems knowing that won't change your mind but still good to get it out there

Interesting. Well it turns out we haven't been refusing to name things as e18e, we are not trying to hide it. So that solves that. Sorry you thought that was the case though.

Nobody has tried to hide what we do. That defeats the purpose!

Hmm I'm not sure why you think I'm afraid of something. It hasn't crossed my mind to be afraid of naming something e18e - we do it quite often. The feature you're talking about directly links to e18e too.
Anyone can suggest a change to the list and anyone can discuss it. We then go with consensus

Indeed we do. And the entries of that list are suggested by the wider community - not always people within the e18e community. We maintain the list, the wider community suggests entries

In this case, maybe we could argue that node should implement the existing clipboard API browsers have 👀

Unfortunately that's not true though. Many of the entries in the e18e data set are added or suggested by people outside of the e18e community. So it can't be that wording either.
"Some people in the wider community flagged..." 😄

Hm, yeah it's not for that purpose of course. It was just added to roughly have the same shape and support as the one we are replacing. To make migration easier.
I agree you should just use the clipboard API if you're targeting browsers.

Yes please 😄

It's the install size via npm
The browser entry point is just a pass through to the clipboard API
It's so you can use the same API regardless of node vs browser. But admittedly I don't know how many such use cases exist. It was just a compat decision to make migration easy

Just compatibility really. It's only a pass through and the package we were replacing had it, so we figured why not

GitHub - tinylibs/tinyclip: A tiny, cross-platform clipboard utility. A tiny, cross-platform clipboard utility. Contribute to tinylibs/tinyclip development by creating an account on GitHub.

a new tinylibs library arrives: tinyclip! 📋

we didn't want to pull in ~2MB to use the system clipboard, so @florian-lefebvre.dev and i paired on making this lighter alternative.

6.7KB, 0 dependencies - supports WSL/macos/linux/windows

there's some hackery to make CORS work in GH pages, and the history (`?q=`) is borked a bit. but seems to work enough!

i saw the interactive xkcd on hackernews and decided to make it render a real npm graph

it uses webcontainers to `npm i {pkg}`, then renders the bricks based on the dep tree scaled by disk size

Very busy month of travel 👀

Heading to Toronto tomorrow, then SF next week, then Vancouver the week after that!

If I forget to reach out to you about catching up, ping me! 🙏

the one day im back before im travelling again and my building has no water 😅

`stringify-object`

> Stringify an object/array like JSON.stringify just without all the double-quotes

a graph showing a flat trend of a package staying the same size until the latest version, at which point it spikes to 579KB (previously 18KB)